The patch titled
vmalloc: remove confusing comment on vwrite()
has been removed from the -mm tree. Its filename was
vmalloc-remove-confusing-comment-on-vwrite.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: vmalloc: remove confusing comment on vwrite()
From: Namhyung Kim <namhyung@xxxxxxxxx>
KM_USER1 is never used for vwrite() path so the caller doesn't need to
guarantee it is not used. Only the caller should guarantee is KM_USER0
and it is commented already.
Signed-off-by: Namhyung Kim <namhyung@xxxxxxxxx>
Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/vmalloc.c | 2 --
1 file changed, 2 deletions(-)
diff -puN mm/vmalloc.c~vmalloc-remove-confusing-comment-on-vwrite mm/vmalloc.c
--- a/mm/vmalloc.c~vmalloc-remove-confusing-comment-on-vwrite
+++ a/mm/vmalloc.c
@@ -2003,8 +2003,6 @@ finished:
* should know vmalloc() area is valid and can use memcpy().
* This is for routines which have to access vmalloc area without
* any informaion, as /dev/kmem.
- *
- * The caller should guarantee KM_USER1 is not used.
*/
long vwrite(char *buf, char *addr, unsigned long count)
_
Patches currently in -mm which might be from namhyung@xxxxxxxxx are
origin.patch
linux-next.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
