linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: FanJun Kong <bh1scw@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: mhocko@kernel.org, roman.gushchin@linux.dev, shakeelb@google.com,
	Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH] MAINTAINERS: add myself as a memcg reviewer
Date: Wed, 18 May 2022 10:45:15 +0800	[thread overview]
Message-ID: <20220518024515.mafizzgw5atz2ejr@box> (raw)
In-Reply-To: <20220517143320.99649-1-songmuchun@bytedance.com>

On 17 May 22 ◦ 22:33, Muchun Song wrote:
> I have been focusing on mm for the past two years. e.g. developing,
> fixing bugs, reviewing.  I have fixed lots of races (including memcg).
> I would like to help people working on memcg or related by reviewing
> their work.  Let me be Cc'd on patches related to memcg.
> 
I vote for Muchun, not only because he helped me with kernel patch
reviewing/suggesting, but because of his influence and contribution
in the open source community.

He is very patient and skilled(memcg, list_lru, etc),
and is very friendly in the community to answer questions.

Thanks

Fanjun Kong

> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9ce78f2275dc..0d5de0c553aa 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5057,6 +5057,7 @@ M:	Johannes Weiner <hannes@cmpxchg.org>
>  M:	Michal Hocko <mhocko@kernel.org>
>  M:	Roman Gushchin <roman.gushchin@linux.dev>
>  M:	Shakeel Butt <shakeelb@google.com>
> +R:	Muchun Song <songmuchun@bytedance.com>
>  L:	cgroups@vger.kernel.org
>  L:	linux-mm@kvack.org
>  S:	Maintained
> -- 
> 2.11.0
> 


      parent reply	other threads:[~2022-05-18  2:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 14:33 Muchun Song
2022-05-17 14:41 ` Shakeel Butt
2022-05-17 14:56 ` Michal Hocko
2022-05-17 15:05 ` Johannes Weiner
2022-05-17 15:53 ` Roman Gushchin
2022-05-18  2:45 ` FanJun Kong [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=20220518024515.mafizzgw5atz2ejr@box \
    --to=bh1scw@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeelb@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