From: Vlastimil Babka <vbabka@suse.cz>
To: Roman Gushchin <roman.gushchin@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: add myself as a memcg co-maintainer
Date: Wed, 23 Feb 2022 11:25:30 +0100 [thread overview]
Message-ID: <5168dd79-73b5-a642-d266-859a020fae9a@suse.cz> (raw)
In-Reply-To: <20220221233951.659048-1-roman.gushchin@linux.dev>
On 2/22/22 00:39, Roman Gushchin wrote:
> Add myself as a memcg co-maintainer. My primary focus over last few
> years was the kernel memory accounting stack, but I do work on some
> other parts of the memory controller as well.
>
> Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 66aa3a589f6a..ecdb90e99ba7 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4991,6 +4991,7 @@ CONTROL GROUP - MEMORY RESOURCE CONTROLLER (MEMCG)
> M: Johannes Weiner <hannes@cmpxchg.org>
> M: Michal Hocko <mhocko@kernel.org>
> M: Vladimir Davydov <vdavydov.dev@gmail.com>
> +M: Roman Gushchin <roman.gushchin@linux.dev>
> L: cgroups@vger.kernel.org
> L: linux-mm@kvack.org
> S: Maintained
next prev parent reply other threads:[~2022-02-23 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 23:39 [PATCH] MAINTAINERS: add myself as a memcg co-maintainer Roman Gushchin
2022-02-22 10:26 ` Michal Hocko
2022-02-22 11:48 ` Vladimir Davydov
2022-02-22 16:38 ` Roman Gushchin
2022-02-23 10:25 ` Vlastimil Babka [this message]
2022-02-23 18:56 ` Johannes Weiner
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=5168dd79-73b5-a642-d266-859a020fae9a@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=vdavydov.dev@gmail.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;
as well as URLs for NNTP newsgroup(s).