From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, rdunlap@infradead.org,
caoyixuan2019@email.szu.edu.cn, akpm@linux-foundation.org
Subject: + mm-vmallocc-fix-a-comment.patch added to -mm tree
Date: Sun, 27 Feb 2022 13:59:03 -0800 [thread overview]
Message-ID: <20220227215904.2404EC340F0@smtp.kernel.org> (raw)
The patch titled
Subject: mm/vmalloc.c: fix a comment
has been added to the -mm tree. Its filename is
mm-vmallocc-fix-a-comment.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/mm-vmallocc-fix-a-comment.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/mm-vmallocc-fix-a-comment.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: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
Subject: mm/vmalloc.c: fix a comment
Link: https://lkml.kernel.org/r/20220227084544.4681-1-caoyixuan2019@email.szu.edu.cn
Signed-off-by: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
Cc: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/vmalloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/vmalloc.c~mm-vmallocc-fix-a-comment
+++ a/mm/vmalloc.c
@@ -2886,7 +2886,7 @@ vm_area_alloc_pages(gfp_t gfp, int nid,
/* memory allocation should consider mempolicy, we can't
* wrongly use nearest node when nid == NUMA_NO_NODE,
* otherwise memory may be allocated in only one node,
- * but mempolcy want to alloc memory by interleaving.
+ * but mempolicy want to alloc memory by interleaving.
*/
if (IS_ENABLED(CONFIG_NUMA) && nid == NUMA_NO_NODE)
nr = alloc_pages_bulk_array_mempolicy(bulk_gfp,
_
Patches currently in -mm which might be from caoyixuan2019@email.szu.edu.cn are
tools-vm-page_owner_sortc-delete-invalid-duplicate-code.patch
documentation-vm-page_ownerrst-fix-commends.patch
mm-page_ownerc-record-tgid.patch
tools-vm-page_owner_sortc-fix-the-instructions-for-use.patch
mm-vmallocc-fix-a-comment.patch
reply other threads:[~2022-02-27 21:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220227215904.2404EC340F0@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=caoyixuan2019@email.szu.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.