From: Mike Kravetz <mike.kravetz@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH] MAINTAINERS: remove hugetlb maintainer Mike Kravetz
Date: Wed, 20 Dec 2023 14:34:17 -0800 [thread overview]
Message-ID: <20231220223417.GB3505@monkey> (raw)
In-Reply-To: <20231220142655.e8797dfc0fff619f12bff53a@linux-foundation.org>
On 12/20/23 14:26, Andrew Morton wrote:
> On Wed, 20 Dec 2023 14:08:43 -0800 Mike Kravetz <mike.kravetz@oracle.com> 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.
>
> Sigh. Thanks Mike.
>
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -9762,7 +9762,6 @@ F: Documentation/networking/device_drivers/ethernet/huawei/hinic.rst
> > F: drivers/net/ethernet/huawei/hinic/
> >
> > HUGETLB SUBSYSTEM
> > -M: Mike Kravetz <mike.kravetz@oracle.com>
> > M: Muchun Song <muchun.song@linux.dev>
> > L: linux-mm@kvack.org
> > S: Maintained
>
> Your patch is buggy.
Figures :)
>
> --- a/CREDITS~maintainers-remove-hugetlb-maintainer-mike-kravetz-fix
> +++ a/CREDITS
> @@ -2126,6 +2126,10 @@ S: 2213 La Terrace Circle
> S: San Jose, CA 95123
> S: USA
>
> +N: Mike Kravetz
> +E: mike.kravetz@oracle.com
> +D: Maintenance and development of the hugetlb subsystem
> +
> N: Andreas S. Krebs
> E: akrebs@altavista.net
> D: CYPRESS CY82C693 chipset IDE, Digital's PC-Alpha 164SX boards
> _
>
> if that's OK?
Sure, I never noticed the CREDITS file.
--
Mike Kravetz
next prev parent reply other threads:[~2023-12-20 22:39 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 [this message]
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
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=20231220223417.GB3505@monkey \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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
all inboxes | Powered by JetHome®