From: Zhenghui Hao <zhenghui.hao@qq.com>
To: linux-mm@kvack.org
Cc: Zhenghui Hao <zhenghui.hao@qq.com>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH] mm/hugetlb: fix misspelled parameter names in comment
Date: Tue, 15 Sep 2026 16:20:29 +0800 [thread overview]
Message-ID: <tencent_034C6FC23D4817C40657E5F17F64E260A009@qq.com> (raw)
The comment above hugepages_setup() refers to "hugepagsz" and
"default_hugepagsz", but the parameters parsed by this code are
"hugepagesz" and "default_hugepagesz". Fix the spelling and also drop
the redundant spaces so the comment reads normally.
No functional change.
Signed-off-by: Zhenghui Hao <zhenghui.hao@qq.com>
---
mm/hugetlb.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index 4f6f58bf3db6..68b97893a376 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -4268,9 +4268,9 @@ static __init void hugetlb_parse_params(void)
/*
* hugepages command line processing
- * hugepages normally follows a valid hugepagsz or default_hugepagsz
- * specification. If not, ignore the hugepages value. hugepages can also
- * be the first huge page command line option in which case it implicitly
+ * hugepages normally follows a valid hugepagesz or default_hugepagesz
+ * specification. If not, ignore the hugepages value. hugepages can also
+ * be the first huge page command line option in which case it implicitly
* specifies the number of huge pages for the default size.
*/
static int __init hugepages_setup(char *s)
--
2.53.0
next reply other threads:[~2026-09-15 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 8:20 Zhenghui Hao [this message]
2026-09-15 8:35 ` Muchun Song
2026-09-16 1:23 ` SJ Park
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=tencent_034C6FC23D4817C40657E5F17F64E260A009@qq.com \
--to=zhenghui.hao@qq.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®