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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux