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 2/2] mm/hugetlb_cgroup: add trailing #endif comment for include guard
Date: Thu, 1 Oct 2026 20:37:47 +0800 [thread overview]
Message-ID: <20261001123747.634845-2-lienze@kylinos.cn> (raw)
In-Reply-To: <20261001123747.634845-1-lienze@kylinos.cn>
The final #endif that closes the _LINUX_HUGETLB_CGROUP_H include guard
is left without a comment. Add the macro name to the comment for
consistency and easier navigation.
Signed-off-by: Enze Li <lienze@kylinos.cn>
---
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 16d72c8c71f6..b4e0958eabf3 100644
--- a/include/linux/hugetlb_cgroup.h
+++ b/include/linux/hugetlb_cgroup.h
@@ -268,4 +268,4 @@ static inline void hugetlb_cgroup_migrate(struct folio *old_folio,
}
#endif /* CONFIG_CGROUP_HUGETLB */
-#endif
+#endif /* _LINUX_HUGETLB_CGROUP_H */
--
2.25.1
next prev parent 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 [PATCH 1/2] MAINTAINERS: add include/linux/hugetlb_cgroup.h to HUGETLB SUBSYSTEM Enze Li
2026-10-01 12:37 ` Enze Li [this message]
2026-10-01 13:18 ` [PATCH 2/2] mm/hugetlb_cgroup: add trailing #endif comment for include guard 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-2-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
all inboxes | Powered by JetHome®