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
..
boot	kbuild: drop redundant "PHONY += FORCE"	2016-04-20 10:38:40 +02:00
configs	unicore32: use the new LED disk activity trigger	2016-06-27 08:58:42 +02:00
include	treewide: remove current_text_addr	2018-10-31 08:54:12 -07:00
kernel	memblock: stop using implicit alignment to SMP_CACHE_BYTES	2018-10-31 08:54:16 -07:00
lib	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
mm	mm: remove include/linux/bootmem.h	2018-10-31 08:54:16 -07:00
.gitignore
Kconfig	dma-mapping: always build the direct mapping code	2018-12-13 21:06:11 +01:00
Kconfig.debug	Kconfig: consolidate the "Kernel hacking" menu	2018-08-02 08:06:48 +09:00
Makefile	unicore32: Use full path in KBUILD_IMAGE definition	2017-03-20 22:42:21 +09:00