mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: Enze Li <lienze@kylinos.cn>
Cc: osalvador@suse.de, david@kernel.org, akpm@linux-foundation.org,
	sj@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	enze.li@gmx.com, Joe Perches <joe@perches.com>
Subject: Re: [PATCH v2 1/2] MAINTAINERS: cover all hugetlb headers under HUGETLB SUBSYSTEM
Date: Mon, 5 Oct 2026 07:28:14 +0200	[thread overview]
Message-ID: <051798AB-A30D-4EF3-8B7D-DC235177BA00@linux.dev> (raw)
In-Reply-To: <20261003060029.2152489-1-lienze@kylinos.cn>



> On Oct 3, 2026, at 08:00, Enze Li <lienze@kylinos.cn> wrote:
> 
> The HUGETLB SUBSYSTEM F: entries list include/linux/hugetlb.h
> explicitly, but other hugetlb headers are not covered, so
> get_maintainer.pl does not attribute them to the hugetlb maintainers.
> 
> Enumerating headers by hand is also fragile: any header not listed (such
> as hugetlb_cgroup.h) falls outside the subsystem.  Joe Perches suggested
> using a glob F: entry, which covers all current and future hugetlb
> headers in one line and avoids the gap.
> 
> Suggested-by: Joe Perches <joe@perches.com>
> Signed-off-by: Enze Li <lienze@kylinos.cn>

Acked-by: Muchun Song <muchun.song@linux.dev>

Thanks.


      parent reply	other threads:[~2026-10-05  5:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03  6:00 Enze Li
2026-10-03  6:00 ` [PATCH v2 2/2] mm/hugetlb_cgroup: add trailing #endif comment for include guard Enze Li
2026-10-03 14:17 ` [PATCH v2 1/2] MAINTAINERS: cover all hugetlb headers under HUGETLB SUBSYSTEM David Hildenbrand (Arm)
2026-10-03 17:43 ` SJ Park
2026-10-05  5:28 ` 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=051798AB-A30D-4EF3-8B7D-DC235177BA00@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=enze.li@gmx.com \
    --cc=joe@perches.com \
    --cc=lienze@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=osalvador@suse.de \
    --cc=sj@kernel.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 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®