From: Mandeep Singh Baines <msb@chromium.org>
To: Tejun Heo <tj@kernel.org>, Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/5] cgroup: some cleanups of cgroup_attach_proc
Date: Tue, 20 Dec 2011 15:14:28 -0800 [thread overview]
Message-ID: <1324422873-31001-1-git-send-email-msb@chromium.org> (raw)
Hello,
This series is a series of cleanups to cgroup_attach_proc. The
series will apply cleanly against cgroup/for-3.3.
There may be some collisions once Frederic's series is applied:
https://lkml.org/lkml/2011/12/20/260
So I may need to resend.
[1 V3] cgroup: remove redundate get/put of old css_set from migrate
[2] cgroup: remove redundant get/put of task struct
[3] cgroup: only need to check oldcgrp==newgrp once
[4] cgroup: remove extra calls to find_existing_css_set
[5] cgroup: separate out cgroup_attach_proc error handling code
Regards,
Mandeep
next reply other threads:[~2011-12-20 23:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 23:14 Mandeep Singh Baines [this message]
2011-12-20 23:14 ` [PATCH 1/5 V3] cgroup: remove redundate get/put of old css_set from migrate Mandeep Singh Baines
2011-12-20 23:18 ` Tejun Heo
2011-12-20 23:41 ` Mandeep Singh Baines
2011-12-20 23:42 ` Tejun Heo
2011-12-20 23:46 ` Tejun Heo
2011-12-21 1:10 ` Li Zefan
2011-12-20 23:14 ` [PATCH 2/5] cgroup: remove redundant get/put of task struct Mandeep Singh Baines
2011-12-20 23:23 ` Tejun Heo
2011-12-21 0:04 ` Mandeep Singh Baines
2011-12-20 23:14 ` [PATCH 3/5] cgroup: only need to check oldcgrp==newgrp once Mandeep Singh Baines
2011-12-21 1:29 ` Li Zefan
2011-12-20 23:14 ` [PATCH 4/5] cgroup: remove extra calls to find_existing_css_set Mandeep Singh Baines
2011-12-20 23:30 ` Tejun Heo
2011-12-20 23:47 ` Mandeep Singh Baines
2011-12-20 23:14 ` [PATCH 5/5] cgroup: separate out cgroup_attach_proc error handling code Mandeep Singh Baines
2011-12-20 23:35 ` Tejun Heo
2011-12-21 0:02 ` Mandeep Singh Baines
2011-12-21 0:13 ` Tejun Heo
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=1324422873-31001-1-git-send-email-msb@chromium.org \
--to=msb@chromium.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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
all inboxes | Powered by JetHome®