From: Mina Almasry <almasrymina@google.com>
To: David Rientjes <rientjes@google.com>
Cc: David Hildenbrand <david@redhat.com>,
James Houghton <jthoughton@google.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Muchun Song <songmuchun@bytedance.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: remove hugetlb maintainer Mike Kravetz
Date: Thu, 21 Dec 2023 11:49:02 -0800 [thread overview]
Message-ID: <CAHS8izOoWCQr5cD0Dyw_sMd3Jp2MnDH8spAqLn7F_Afh_kEQPg@mail.gmail.com> (raw)
In-Reply-To: <ab373102-9192-e3bd-e829-63048365b3ca@google.com>
On Thu, Dec 21, 2023 at 11:45 AM David Rientjes <rientjes@google.com> wrote:
>
> On Wed, 20 Dec 2023, David Hildenbrand wrote:
>
> > On 20.12.23 23:08, Mike Kravetz wrote:
> > > I am stepping away from my role as hugetlb maintainer. There should be
> > > no gap in coverage as Muchun Song is also a hugetlb maintainer.
> > >
> > > Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
> >
> > Mike, thank you so much for all your hard work over all these years!
> >
> > It's been a real pleasure working with you every time our upstream paths
> > crossed! :)
> >
>
> +100.
>
> Mike, your ownership, expertise, and collaboration have been deeply needed
> but also very motivating and inspiring.
>
> You know how I feel about it. It's been a pleasure.
Indeed, it was a pleasure collaborating with you on the hugetlb_cgroup
stuff. Thank you very much Mike.
--
Thanks,
Mina
next prev parent reply other threads:[~2023-12-21 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 22:08 Mike Kravetz
2023-12-20 22:26 ` Andrew Morton
2023-12-20 22:34 ` Mike Kravetz
2023-12-20 22:30 ` Frank van der Linden
2023-12-20 22:53 ` David Hildenbrand
2023-12-21 19:45 ` David Rientjes
2023-12-21 19:49 ` Mina Almasry [this message]
2023-12-21 2:28 ` 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=CAHS8izOoWCQr5cD0Dyw_sMd3Jp2MnDH8spAqLn7F_Afh_kEQPg@mail.gmail.com \
--to=almasrymina@google.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jthoughton@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rientjes@google.com \
--cc=songmuchun@bytedance.com \
/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