Christoph Hellwig 512317401f dma-mapping: always use VM_DMA_COHERENT for generic DMA remap ... Currently the generic dma remap allocator gets a vm_flags passed by the caller that is a little confusing. We just introduced a generic vmalloc-level flag to identify the dma coherent allocations, so use that everywhere and remove the now pointless argument. Signed-off-by: Christoph Hellwig <hch@lst.de>		2019-09-04 11:13:20 +02:00
..
boot	Xtensa updates for v5.3:	2019-07-16 12:17:07 -07:00
configs	xtensa: virt: add defconfig and DTS	2019-07-08 14:32:06 -07:00
include	Merge branch 'akpm' (patches from Andrew)	2019-07-17 08:58:04 -07:00
kernel	dma-mapping: always use VM_DMA_COHERENT for generic DMA remap	2019-09-04 11:13:20 +02:00
lib	xtensa: abstract 'entry' and 'retw' in assembly code	2019-07-08 10:04:48 -07:00
mm	Xtensa updates for v5.3:	2019-07-16 12:17:07 -07:00
oprofile	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
platforms	treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 152	2019-05-30 11:26:32 -07:00
variants	xtensa: add test_kc705_be variant	2018-08-20 12:34:45 -07:00
Kconfig	dma-mapping: remove CONFIG_ARCH_NO_COHERENT_DMA_MMAP	2019-09-04 11:13:18 +02:00
Kconfig.debug	Kconfig: consolidate the "Kernel hacking" menu	2018-08-02 08:06:48 +09:00
Makefile	xtensa: generate uapi header and syscall table header files	2018-12-02 23:45:41 -08:00