From: Tejun Heo <tj@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, john@johnmccutchan.com,
rlove@rlove.org, eparis@parisplace.org, serge.hallyn@ubuntu.com,
lennart@poettering.net, kay@vrfy.org, lizefan@huawei.com,
cgroups@vger.kernel.org, containers@lists.linux-foundation.org
Subject: Re: [PATCHSET cgroup/for-3.16] cgroup: implement cgroup.populated
Date: Tue, 15 Apr 2014 12:18:28 -0400 [thread overview]
Message-ID: <20140415161828.GA30990@htj.dyndns.org> (raw)
In-Reply-To: <20140414222658.GA18152@kroah.com>
Hello, Greg.
On Mon, Apr 14, 2014 at 03:26:58PM -0700, Greg KH wrote:
> Do you want me to pull this branch into my tree for 3.16 now? I have no
> objection to you taking it, if that's easier for you, which ever is fine
> for me.
I think the best way to proceed would be applying 1-2 to
driver-core-next and then base cgroup/for-3.16 on top of it, but I'd
like to get some feedback from inotify people before proceeding.
Thanks.
--
tejun
next prev parent reply other threads:[~2014-04-15 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 15:07 Tejun Heo
2014-04-09 15:07 ` [PATCH 1/3] kernfs: implement kernfs_root->supers list Tejun Heo
2014-04-09 15:07 ` [PATCH 2/3] kernfs: make kernfs_notify() trigger inotify events too Tejun Heo
2014-04-09 15:07 ` [PATCH 3/3] cgroup: implement cgroup.subtree_populated for the default hierarchy Tejun Heo
2014-04-10 3:08 ` Serge E. Hallyn
2014-04-10 13:08 ` Tejun Heo
2014-04-10 14:04 ` Serge Hallyn
2014-04-10 14:19 ` Tejun Heo
2014-04-11 9:00 ` Li Zefan
2014-04-14 21:31 ` [PATCHSET cgroup/for-3.16] cgroup: implement cgroup.populated Tejun Heo
2014-04-14 22:26 ` Greg KH
2014-04-15 16:18 ` Tejun Heo [this message]
2014-04-23 15:16 ` Tejun Heo
2014-04-25 18:57 ` Greg KH
2014-04-25 22:30 ` 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=20140415161828.GA30990@htj.dyndns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=eparis@parisplace.org \
--cc=gregkh@linuxfoundation.org \
--cc=john@johnmccutchan.com \
--cc=kay@vrfy.org \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=rlove@rlove.org \
--cc=serge.hallyn@ubuntu.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®