From: Tejun Heo <tj@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jens Axboe <axboe@kernel.dk>,
Josh Boyer <jwboyer@fedoraproject.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
John McCutchan <john@johnmccutchan.com>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
Robert Love <rlove@rlove.org>, Eric Paris <eparis@parisplace.org>,
Brian Lane <bcl@redhat.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
Date: Wed, 2 Jul 2014 10:14:16 -0400 [thread overview]
Message-ID: <20140702141416.GA23275@htj.dyndns.org> (raw)
In-Reply-To: <20140701205148.GA26542@kroah.com>
Hello,
On Tue, Jul 01, 2014 at 01:51:48PM -0700, Greg Kroah-Hartman wrote:
> Looks good to me, do you want to take this with your other kernfs
> patches for 3.16-final? Or if you don't have that, I can take it
> through my tree, it's your choice, either is fine for me.
>
> If you want it in your tree, feel free to add:
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
The other kernfs changes are cgroup specific and in
cgroup/for-3.16-fixes. I think this one fits better in the driver
core tree. Can you please route it?
Thanks!
--
tejun
next prev parent reply other threads:[~2014-07-02 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+5PVA4h2hQJLrAm4eEZ8oUgGiAjq2y5eAyBcJWxK_FiQXnuQg@mail.gmail.com>
2014-06-29 8:26 ` virt_blk BUG: sleeping function called from invalid context Michael S. Tsirkin
2014-06-29 19:32 ` Christoph Hellwig
[not found] ` <20140629193222.GA7030@lst.de>
2014-06-29 20:47 ` Michael S. Tsirkin
2014-06-29 20:55 ` Jens Axboe
2014-06-30 20:17 ` Tejun Heo
2014-07-01 20:41 ` [PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts Tejun Heo
2014-07-01 20:51 ` Greg Kroah-Hartman
2014-07-02 14:14 ` Tejun Heo [this message]
2014-07-02 16:31 ` Greg Kroah-Hartman
2014-07-02 5:53 ` Michael S. Tsirkin
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=20140702141416.GA23275@htj.dyndns.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=bcl@redhat.com \
--cc=eparis@parisplace.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=john@johnmccutchan.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rlove@rlove.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).