dma-mapping: use obj-y instead of lib-y for generic dma ops

We already have exact config symbols to select the direct, non-coherent,
or virt dma ops.  So use the normal obj- scheme to select them.

Signed-off-by: Christoph Hellwig <hch@lst.de>
This commit is contained in:
Christoph Hellwig 2018-06-14 08:49:34 +02:00
parent be779f03d5
commit e37460c1ca
1 changed files with 3 additions and 3 deletions

View File

@ -29,9 +29,9 @@ lib-y := ctype.o string.o vsprintf.o cmdline.o \
lib-$(CONFIG_PRINTK) += dump_stack.o
lib-$(CONFIG_MMU) += ioremap.o
lib-$(CONFIG_SMP) += cpumask.o
lib-$(CONFIG_DMA_DIRECT_OPS) += dma-direct.o
lib-$(CONFIG_DMA_NONCOHERENT_OPS) += dma-noncoherent.o
lib-$(CONFIG_DMA_VIRT_OPS) += dma-virt.o
obj-$(CONFIG_DMA_DIRECT_OPS) += dma-direct.o
obj-$(CONFIG_DMA_NONCOHERENT_OPS) += dma-noncoherent.o
obj-$(CONFIG_DMA_VIRT_OPS) += dma-virt.o
lib-y += kobject.o klist.o
obj-y += lockref.o