From: Muchun Song <muchun.song@linux.dev>
To: Enze Li <lienze@kylinos.cn>
Cc: osalvador@suse.de, david@kernel.org, akpm@linux-foundation.org,
corbet@lwn.net, linux-mm@kvack.org, linux-doc@vger.kernel.org,
enze.li@gmx.com, Enze Li <lienze@kylinos.cn>
Subject: Re: [PATCH] docs: hugetlbpage.rst: fix typo in per-node attribute description
Date: Tue, 6 Oct 2026 11:06:02 +0200 [thread overview]
Message-ID: <741903F2-2935-4AD0-A46B-63457E6E7393@linux.dev> (raw)
In-Reply-To: <20261003161125.40485-1-lienze@kylinos.cn>
> On Oct 3, 2026, at 18:12, Enze Li <lienze@kylinos.cn> wrote:
>
> The per-node hugepages section writes the free_hugepages and
> surplus_hugepages file names with stray trailing quotes. Quote the real
> names as inline literals instead.
>
> Signed-off-by: Enze Li <lienze@kylinos.cn>
Acked-by: Muchun Song <muchun.song@linux.dev>
Thanks
prev parent reply other threads:[~2026-10-06 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 16:11 [PATCH] docs: hugetlbpage.rst: fix typo in per-node attribute description Enze Li
2026-10-06 9:06 ` Muchun Song [this message]
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=741903F2-2935-4AD0-A46B-63457E6E7393@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=enze.li@gmx.com \
--cc=lienze@kylinos.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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