nommu-remove-__gfp_highmem-in-vmalloc-vzalloc.patch removed from -mm tree
The patch titled
Subject: nommu: remove __GFP_HIGHMEM in vmalloc/vzalloc
has been removed from the -mm tree. Its filename was
nommu-remove-__gfp_highmem-in-vmalloc-vzalloc.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Chen Li <[email protected]>
Subject: nommu: remove __GFP_HIGHMEM in vmalloc/vzalloc
mm/nommu.c:
void *__vmalloc(unsigned long size, gfp_t gfp_mask)
{
/*
* You can't specify __GFP_HIGHMEM with kmalloc() since kmalloc()
* returns only a logical address.
*/
return kmalloc(size, (gfp_mask | __GFP_COMP) & ~__GFP_HIGHMEM);
}nommu's __vmalloc just uses kmalloc internally and elimitates __GFP_HIGHMEM, so it makes no sense to add __GFP_HIGHMEM for nommu's vmalloc/vzalloc.
[[email protected]: coding style fixes]
Signed-off-by Chen Li <[email protected]>
Reviewed-by Matthew Wilcox (Oracle) <[email protected]>
Reviewed-by David Hildenbrand <[email protected]>
Cc Greg Ungerer <[email protected]>
Cc Geert Uytterhoeven <[email protected]>
Signed-off-by Andrew Morton <[email protected]>
---
mm/nommu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
mm/nommu.c renamed from mm/nommu.c~nommu-remove-__gfp_highmem-in-vmalloc-vzalloc +2 -2
@@ -223,7 +223,7 @@ long vread(char *buf, char *addr, unsign*/ void *vmalloc (unsigned long size) { -return __vmalloc (size,GFP_KERNEL | __GFP_HIGHMEM); +return __vmalloc (size,GFP_KERNEL ); }EXPORT_SYMBOL (vmalloc);
@@ -241,7 +241,7 @@ EXPORT_SYMBOL(vmalloc);*/ void *vzalloc (unsigned long size) { -return __vmalloc (size,GFP_KERNEL | __GFP_HIGHMEM | __GFP_ZERO); +return __vmalloc (size,GFP_KERNEL | __GFP_ZERO); }EXPORT_SYMBOL (vzalloc);
_
Patches currently in -mm which might be from [email protected] are