The patch titled
Subject: kernel/utsname.c: fix wrong comment about clone_uts_ns()
has been added to the -mm tree. Its filename is
namespaces-utsname-fix-wrong-comment-about-clone_uts_ns.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
Subject: kernel/utsname.c: fix wrong comment about clone_uts_ns()
Fix the wrong comment about the return value of clone_uts_ns()
Signed-off-by: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
Acked-by: Serge Hallyn <serge.hallyn@xxxxxxxxxxxxx>
Cc: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/utsname.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN kernel/utsname.c~namespaces-utsname-fix-wrong-comment-about-clone_uts_ns kernel/utsname.c
--- a/kernel/utsname.c~namespaces-utsname-fix-wrong-comment-about-clone_uts_ns
+++ a/kernel/utsname.c
@@ -30,7 +30,7 @@ static struct uts_namespace *create_uts_
/*
* Clone a new ns copying an original utsname, setting refcount to 1
* @old_ns: namespace to clone
- * Return NULL on error (failure to kmalloc), new ns otherwise
+ * Return ERR_PTR(-ENOMEM) on error (failure to kmalloc), new ns otherwise
*/
static struct uts_namespace *clone_uts_ns(struct user_namespace *user_ns,
struct uts_namespace *old_ns)
_
Patches currently in -mm which might be from yuanhan.liu@xxxxxxxxxxxxxxx are
mm-fix-wrong-comments-about-anon_vma-lock.patch
linux-next.patch
fs-execc-make-bprm_mm_init-static.patch
namespaces-utsname-fix-wrong-comment-about-clone_uts_ns.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
