From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
Balbir Singh <bsingharora@gmail.com>
Subject: Re: [PATCH cgroup/for-3.16] cgroup: clean up MAINTAINERS entries
Date: Wed, 21 May 2014 14:42:07 +0900 [thread overview]
Message-ID: <537C3CAF.5080204@jp.fujitsu.com> (raw)
In-Reply-To: <20140519203339.GE27506@mtj.dyndns.org>
(2014/05/20 5:33), Tejun Heo wrote:
> On Tue, May 13, 2014 at 03:49:58PM -0400, Tejun Heo wrote:
>> There are currently three cgroup related entries in MAINTAINERS. Make
>> the following updates.
>>
>> * Make the names - both cgroup and cpuset - singular. We're mixing
>> singular and plural all over the place for no good reason.
>>
>> * Drop containers@lists.linux-foundation.org from CGROUP. That list
>> doesn't have much to do with cgroup per-se.
>>
>> * Add Documentation field to CGROUP.
>>
>> * Drop mm/*cgroup* from CGROUP. memcg has separate maintainers.
>>
>> * Prefix the controller-specific ones with "CONTROL CGROUP -" and
>> collect cgroup related entries under the core one.
>>
>> * Add (MEMCG) abbreviation to MEMCG entry.
>>
>> * Drop Balbir Singh and KAMEZAWA Hiroyuki from memcg maintainers. It
>> has been quite a while since both actually worked on memcg.
>>
>> Signed-off-by: Tejun Heo <tj@kernel.org>
>
> Applied to cgroup/for-3.16.
>
thank you.
-Kame
next prev parent reply other threads:[~2014-05-21 5:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 19:49 [PATCH cgroup/for-3.16] cgroup: clean up MAINTAINERS entries Tejun Heo
2014-05-19 20:33 ` Tejun Heo
2014-05-21 5:42 ` Kamezawa Hiroyuki [this message]
2014-05-28 7:46 ` Li Zefan
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=537C3CAF.5080204@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mhocko@suse.cz \
--cc=tj@kernel.org \
/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