Marek Szyprowski 6518202970 mm/cma: remove unsupported gfp_mask parameter from cma_alloc() ... cma_alloc() doesn't really support gfp flags other than __GFP_NOWARN, so convert gfp_mask parameter to boolean no_warn parameter. This will help to avoid giving false feeling that this function supports standard gfp flags and callers can pass __GFP_ZERO to get zeroed buffer, what has already been an issue: see commit dd65a941f6 ("arm64: dma-mapping: clear buffers allocated with FORCE_CONTIGUOUS flag"). Link: http://lkml.kernel.org/r/20180709122019eucas1p2340da484acfcc932537e6014f4fd2c29~-sqTPJKij2939229392eucas1p2j@eucas1p2.samsung.com Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> Acked-by: Michal Hocko <mhocko@suse.com> Acked-by: Michał Nazarewicz <mina86@mina86.com> Acked-by: Laura Abbott <labbott@redhat.com> Acked-by: Vlastimil Babka <vbabka@suse.cz> Reviewed-by: Christoph Hellwig <hch@lst.de> Cc: Joonsoo Kim <js1304@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2018-08-17 16:20:32 -07:00
..
Kconfig	…
Makefile	…
coherent.c	…
contiguous.c	mm/cma: remove unsupported gfp_mask parameter from cma_alloc()	2018-08-17 16:20:32 -07:00
debug.c	…
direct.c	dma-mapping: Generalise dma_32bit_limit flag	2018-07-27 19:01:04 +02:00
mapping.c	…
noncoherent.c	dma-noncoherent: add a arch_sync_dma_for_cpu_all hook	2018-06-24 09:27:27 -07:00
swiotlb.c	swiotlb: clean up reporting	2018-07-25 13:33:05 +02:00
virt.c	…