The patch titled
Subject: mm: fix spelling error
has been added to the -mm tree. Its filename is
mm-fix-spelling-error.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-fix-spelling-error.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-fix-spelling-error.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: Hao Lee <haolee.swjtu@xxxxxxxxx>
Subject: mm: fix spelling error
Fix variable name error in comments. No code changes.
Link: http://lkml.kernel.org/r/20170403161655.5081-1-haolee.swjtu@xxxxxxxxx
Signed-off-by: Hao Lee <haolee.swjtu@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/gfp.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN include/linux/gfp.h~mm-fix-spelling-error include/linux/gfp.h
--- a/include/linux/gfp.h~mm-fix-spelling-error
+++ a/include/linux/gfp.h
@@ -313,8 +313,8 @@ static inline bool gfpflags_allow_blocki
/*
* GFP_ZONE_TABLE is a word size bitstring that is used for looking up the
- * zone to use given the lowest 4 bits of gfp_t. Entries are ZONE_SHIFT long
- * and there are 16 of them to cover all possible combinations of
+ * zone to use given the lowest 4 bits of gfp_t. Entries are GFP_ZONES_SHIFT
+ * bits long and there are 16 of them to cover all possible combinations of
* __GFP_DMA, __GFP_DMA32, __GFP_MOVABLE and __GFP_HIGHMEM.
*
* The zone fallback order is MOVABLE=>HIGHMEM=>NORMAL=>DMA32=>DMA.
_
Patches currently in -mm which might be from haolee.swjtu@xxxxxxxxx are
mm-fix-spelling-error.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
