From: David Hildenbrand <david@redhat.com>
To: Vlastimil Babka <vbabka@suse.cz>,
Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Muchun Song <muchun.song@linux.dev>, Peter Xu <peterx@redhat.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Update maintainers for HugeTLB
Date: Tue, 17 Jun 2025 21:06:49 +0200 [thread overview]
Message-ID: <c73fd105-8dc0-4446-84a3-53473c94b1b5@redhat.com> (raw)
In-Reply-To: <8173e254-f129-4f02-98f1-f9b98374a8c4@suse.cz>
On 17.06.25 21:04, Vlastimil Babka wrote:
> On 6/17/25 20:59, Oscar Salvador wrote:
>> Change my role to Maintainer as I am quite involved in HugeTLB development,
>> and will be more so with the upcoming HugetLB-pagewalk unification, so I
>> would like to help Munchun take care of the code.
>> Besides, having two people will help in offloading some pressure.
>>
>> Also add David as a Reviewer since he has quite some knowledge in the field
>> and has already provided valuable feedback.
>>
>> Signed-off-by: Oscar Salvador <osalvador@suse.de>
>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
>
>> ---
>> I also asked Peter Xu to become a R, but I think he is currently too busy to
>> commit to that, but he was happy to be CCed instead :-).
>
> Not sure I understand. R: is the way to get CCd by get_maintainers.pl,
> otherwise only the people who know about this would Cc? (unless they
> forget). Or you mean to be CCd on this patch?
probably CCing him when there are questions on specific patches.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-06-17 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 18:59 Oscar Salvador
2025-06-17 19:03 ` David Hildenbrand
2025-06-17 19:04 ` Vlastimil Babka
2025-06-17 19:06 ` David Hildenbrand [this message]
2025-06-18 2:47 ` Muchun Song
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=c73fd105-8dc0-4446-84a3-53473c94b1b5@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=peterx@redhat.com \
--cc=vbabka@suse.cz \
/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