From: Enze Li <lienze@kylinos.cn>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
ljs@kernel.org, akpm@linux-foundation.org,
enelsonmoore@gmail.com, linux-kernel@vger.kernel.org,
enze.li@gmx.com
Subject: Re: [PATCH] mm/hugetlb_cgroup: add trailing #endif comment for include guard
Date: Thu, 1 Oct 2026 20:20:42 +0800 [thread overview]
Message-ID: <3b2b1d87-bc96-4292-9514-bb263b6496b7@kylinos.cn> (raw)
In-Reply-To: <487f9b69-b314-4133-94f8-733321424e9a@kernel.org>
On 10/1/26 20:01, David Hildenbrand (Arm) wrote:
> On 10/1/26 13:39, Enze Li wrote:
>> 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 */
>>
>> base-commit: 21c3620df8ad362e9f2069ac35577c2a2f782f33
>
> Note that this was not sent to the MM mailing list and/or hugetlb maintainers.
>
> Likely scripts/get_maintainers.pl will help you figure out whom to CC exactly.
>
Thank you, David :) I'll resend this patch to the correct mailing list.
Thanks,
Enze
prev parent reply other threads:[~2026-10-01 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 11:39 Enze Li
2026-10-01 12:01 ` David Hildenbrand (Arm)
2026-10-01 12:20 ` Enze Li [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=3b2b1d87-bc96-4292-9514-bb263b6496b7@kylinos.cn \
--to=lienze@kylinos.cn \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=enelsonmoore@gmail.com \
--cc=enze.li@gmx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@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®