Build failure with DMA_OMAP=m and a caller built-in

Ben Hutchings
2013-01-06T05:26:20Z

[-- Attachment #1: Type: text/plain, Size: 637 bytes --]

Various drivers use omap_dma_filter_fn() but don't depend on DMA_OMAP.
This is fine because there is a trivial inline definition in case
DMA_OMAP is disabled... until the caller is built-in and DMA_OMAP=m.

I tried adding the rather weird 'select DMA_OMAP if DMA_OMAP!=n' to
these drivers' kconfig symbols to promote it to built-in if necessary.
This sort of works but kconfig complains about the circular dependency
and it becomes impossible to disable DMA_OMAP in the 'make nconfig'
menu. So that's not the right thing to do.

Any ideas?

Ben.

--
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]