Re: [PATCH v2 00/21] Allow compile-testing NO_DMA (drivers)

Hi Rob, On Thu, Apr 5, 2018 at 2:32 AM, Rob Herring wrote: > On Fri, Mar 16, 2018 at 8:51 AM, Geert Uytterhoeven > wrote: >> If NO_DMA=y, get_dma_ops() returns a reference to the non-existing >> symbol bad_dma_ops, thus causing a link failure if it

Re: [PATCH v2 00/21] Allow compile-testing NO_DMA (drivers)

On Fri, Mar 16, 2018 at 8:51 AM, Geert Uytterhoeven wrote: > Hi all, > > If NO_DMA=y, get_dma_ops() returns a reference to the non-existing > symbol bad_dma_ops, thus causing a link failure if it is ever used. > > The intention of this is twofold: > 1. To catch

Re: [PATCH v2 00/21] Allow compile-testing NO_DMA (drivers)

> To play it safe, you want to postpone the subsystem patches until the core > part has landed upstream. I will rebase and resubmit after v4.17-rc1. Thanks for the heads up. I'll wait for the rebased patch then and apply it after rc1 for 4.17. signature.asc Description: PGP signature

Re: [PATCH v2 00/21] Allow compile-testing NO_DMA (drivers)

Hi Wolfram, On Fri, Mar 16, 2018 at 10:23 PM, Wolfram Sang wrote: >> To avoid allmodconfig/allyesconfig regressions on NO_DMA=y platforms, >> this (drivers) series should be applied after the previous (core) >> series (but not many people may notice/care ;-) > > I still don't

Re: [PATCH v2 00/21] Allow compile-testing NO_DMA (drivers)

> To avoid allmodconfig/allyesconfig regressions on NO_DMA=y platforms, > this (drivers) series should be applied after the previous (core) > series (but not many people may notice/care ;-) I still don't get if there is a dependency on the core patches. I.e. shall I apply the subsystem patch now

Re: [PATCH v2 00/21] Allow compile-testing NO_DMA (drivers)

On Fri, Mar 16, 2018 at 04:41:57PM +0100, Geert Uytterhoeven wrote: > > | To avoid allmodconfig/allyesconfig regressions on NO_DMA=y platforms, > | this (drivers) series should be applied after the previous (core) > | series (but not many people may notice/care ;-) Oops, didn't notice it :) >

Re: [PATCH v2 00/21] Allow compile-testing NO_DMA (drivers)

Hi Herbert, On Fri, Mar 16, 2018 at 4:14 PM, Herbert Xu wrote: > On Fri, Mar 16, 2018 at 02:51:33PM +0100, Geert Uytterhoeven wrote: >> This patch series: >> - Removes dependencies on HAS_DMA for symbols that already have >> platform dependencies implying

Re: [PATCH v2 00/21] Allow compile-testing NO_DMA (drivers)

On Fri, Mar 16, 2018 at 02:51:33PM +0100, Geert Uytterhoeven wrote: > > This patch series: > - Removes dependencies on HAS_DMA for symbols that already have > platform dependencies implying HAS_DMA. > > To avoid allmodconfig/allyesconfig regressions on NO_DMA=y platforms, > this (drivers)

[PATCH v2 00/21] Allow compile-testing NO_DMA (drivers)

Hi all, If NO_DMA=y, get_dma_ops() returns a reference to the non-existing symbol bad_dma_ops, thus causing a link failure if it is ever used. The intention of this is twofold: 1. To catch users of the DMA API on systems that do no support the DMA mapping API, 2. To avoid