The patch titled
Subject: mm/page_poison: update comment after code moved
has been added to the -mm tree. Its filename is
mm-page_poison-update-comment-after-code-moved.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-page_poison-update-comment-after-code-moved.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-page_poison-update-comment-after-code-moved.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/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
Subject: mm/page_poison: update comment after code moved
mm/debug-pagealloc.c is no more, so of course header now needs to be
updated. This seems like something checkpatch should be able to catch -
worth looking into?
Link: http://lkml.kernel.org/r/20190207191113.14039-1-mst@xxxxxxxxxx
Fixes: 8823b1dbc05f ("mm/page_poison.c: enable PAGE_POISONING as a separate option")
Signed-off-by: Michael S. Tsirkin <mst@xxxxxxxxxx>
Reviewed-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
--- a/include/linux/poison.h~mm-page_poison-update-comment-after-code-moved
+++ a/include/linux/poison.h
@@ -30,7 +30,7 @@
*/
#define TIMER_ENTRY_STATIC ((void *) 0x300 + POISON_POINTER_DELTA)
-/********** mm/debug-pagealloc.c **********/
+/********** mm/page_poison.c **********/
#ifdef CONFIG_PAGE_POISONING_ZERO
#define PAGE_POISON 0x00
#else
_
Patches currently in -mm which might be from mst@xxxxxxxxxx are
mm-page_poison-update-comment-after-code-moved.patch
