Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Enze Li <lienze@kylinos.cn>
To: muchun.song@linux.dev, osalvador@suse.de, david@kernel.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Enze Li <lienze@kylinos.cn>
Subject: [PATCH 1/2] MAINTAINERS: add include/linux/hugetlb_cgroup.h to HUGETLB SUBSYSTEM
Date: Thu,  1 Oct 2026 20:37:46 +0800	[thread overview]
Message-ID: <20261001123747.634845-1-lienze@kylinos.cn> (raw)

include/linux/hugetlb_cgroup.h is the header file paired with
mm/hugetlb_cgroup.c, but it is not listed among the HUGETLB SUBSYSTEM
F: entries.  As a result get_maintainer.pl does not attribute the header
to the hugetlb maintainers explicitly.  Add the F: entry so the file is
covered.

Signed-off-by: Enze Li <lienze@kylinos.cn>
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 596efa354ea2..6c210e90722f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12097,6 +12097,7 @@ F:	Documentation/mm/hugetlbfs_reserv.rst
 F:	Documentation/mm/vmemmap_dedup.rst
 F:	fs/hugetlbfs/
 F:	include/linux/hugetlb.h
+F:	include/linux/hugetlb_cgroup.h
 F:	include/linux/vmemmap-optimization.h
 F:	include/trace/events/hugetlbfs.h
 F:	mm/hugetlb.c
-- 
2.25.1



             reply	other threads:[~2026-10-01 12:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 12:37 Enze Li [this message]
2026-10-01 12:37 ` [PATCH 2/2] mm/hugetlb_cgroup: add trailing #endif comment for include guard Enze Li
2026-10-01 13:18   ` David Hildenbrand (Arm)
2026-10-02  2:54   ` Muchun Song
2026-10-02 18:27   ` SJ Park
2026-10-01 12:50 ` [PATCH 1/2] MAINTAINERS: add include/linux/hugetlb_cgroup.h to HUGETLB SUBSYSTEM Muchun Song
2026-10-01 13:18 ` David Hildenbrand (Arm)
2026-10-02 17:37 ` Joe Perches
2026-10-02 18:48   ` David Hildenbrand (Arm)

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=20261001123747.634845-1-lienze@kylinos.cn \
    --to=lienze@kylinos.cn \
    --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