From: Lorenzo Stoakes <ljs@kernel.org>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pedro Falcato <pfalcato@suse.de>,
Anthony Yznaga <anthony.yznaga@oracle.com>
Subject: Re: [PATCH] mm: hugetlb: correct CONFIG_CGROUP_HUGETLB macro name in comment
Date: Mon, 29 Jun 2026 11:25:23 +0100 [thread overview]
Message-ID: <akJIBNv36YtDRsYj@lucifer> (raw)
In-Reply-To: <20260616000135.62815-1-enelsonmoore@gmail.com>
On Mon, Jun 15, 2026 at 05:01:31PM -0700, Ethan Nelson-Moore wrote:
> A comment in <linux/hugetlb_cgroup.h> incorrectly refers to
> CONFIG_MEM_RES_CTLR_HUGETLB, which has never existed in the kernel,
> instead of CONFIG_CGROUP_HUGETLB. Correct it.
>
> Discovered while searching for CONFIG_* symbols referenced in code but
> not defined in any Kconfig file.
>
> Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
LGTM, so:
Reviewed-by: Lorenzo Stoakes <ljs@kernel.org>
> ---
> include/linux/hugetlb_cgroup.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/hugetlb_cgroup.h b/include/linux/hugetlb_cgroup.h
> index e5d64b8b59c2..16d72c8c71f6 100644
> --- a/include/linux/hugetlb_cgroup.h
> +++ b/include/linux/hugetlb_cgroup.h
> @@ -267,5 +267,5 @@ static inline void hugetlb_cgroup_migrate(struct folio *old_folio,
> {
> }
>
> -#endif /* CONFIG_MEM_RES_CTLR_HUGETLB */
> +#endif /* CONFIG_CGROUP_HUGETLB */
> #endif
> --
> 2.43.0
>
Cheers, Lorenzo
prev parent reply other threads:[~2026-06-29 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260616000135.62815-1-enelsonmoore@gmail.com>
2026-06-23 7:40 ` [PATCH] mm: hugetlb: correct CONFIG_CGROUP_HUGETLB macro name in comment David Hildenbrand (Arm)
2026-06-29 10:25 ` Lorenzo Stoakes [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=akJIBNv36YtDRsYj@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anthony.yznaga@oracle.com \
--cc=david@kernel.org \
--cc=enelsonmoore@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=pfalcato@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