linux/arch/sh
Christoph Hellwig 3731c3d477 dma-mapping: always build the direct mapping code
All architectures except for sparc64 use the dma-direct code in some
form, and even for sparc64 we had the discussion of a direct mapping
mode a while ago.  In preparation for directly calling the direct
mapping code don't bother having it optionally but always build the
code in.  This is a minor hardship for some powerpc and arm configs
that don't pull it in yet (although they should in a relase ot two),
and sparc64 which currently doesn't need it at all, but it will
reduce the ifdef mess we'd otherwise need significantly.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
Tested-by: Jesper Dangaard Brouer <brouer@redhat.com>
Tested-by: Tony Luck <tony.luck@intel.com>
2018-12-13 21:06:11 +01:00
..
boards Devicetree updates for 4.20: 2018-10-26 12:09:58 -07:00
boot
cchips
configs
drivers PCI: Call dma_debug_add_bus() for pci_bus_type from PCI core 2018-07-30 15:58:01 -05:00
include treewide: remove current_text_addr 2018-10-31 08:54:12 -07:00
kernel sh: prefer _THIS_IP_ to current_text_addr 2018-08-17 16:20:27 -07:00
lib
lib64
math-emu
mm mm: remove include/linux/bootmem.h 2018-10-31 08:54:16 -07:00
oprofile
tools
Kconfig dma-mapping: always build the direct mapping code 2018-12-13 21:06:11 +01:00
Kconfig.cpu
Kconfig.debug Kconfig: consolidate the "Kernel hacking" menu 2018-08-02 08:06:48 +09:00
Makefile kbuild: rename LDFLAGS to KBUILD_LDFLAGS 2018-08-24 08:22:08 +09:00