From: NeilBrown <neilb@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH 0/2 V3] Allow access to sysfs attributes without mem allocations.
Date: Mon, 13 Oct 2014 21:21:57 +1100 [thread overview]
Message-ID: <20141013212157.4e68147c@notabene.brown> (raw)
In-Reply-To: <20141013083512.GA29706@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
On Mon, 13 Oct 2014 10:35:12 +0200 Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> On Mon, Oct 13, 2014 at 04:41:28PM +1100, NeilBrown wrote:
> > Hi Greg,
> > please consider these two patches for a future release.
> > They now have
> > Reviewed-by: Tejun Heo <tj@kernel.org>
> > and I've addressed Tejun's final nits.
> >
> > Thanks Tejun for your review and comments.
> >
> > As soon as they appear in an -rc1, I'll submit updates to md to use
> > the new functionality for the -rc2.
>
> It will have to wait until 3.19-rc1, I'll queue it up in my tree after
> 3.18-rc1 is out. You can merge from my driver-core tree into yours if
> you want to build off of it, as my tree will not be rebased.
>
All fine with me - thanks a lot.
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2014-10-13 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 5:41 [PATCH 0/2 V3] Allow access to sysfs attributes without mem allocations NeilBrown
2014-10-13 5:41 ` [PATCH 1/2] sysfs/kernfs: allow attributes to request write buffer be pre-allocated NeilBrown
2014-10-13 5:41 ` [PATCH 2/2] sysfs/kernfs: make read requests on pre-alloc files use the buffer NeilBrown
2014-10-14 5:57 ` [PATCH 2/2 - revised] " NeilBrown
2014-10-13 8:35 ` [PATCH 0/2 V3] Allow access to sysfs attributes without mem allocations Greg Kroah-Hartman
2014-10-13 10:21 ` NeilBrown [this message]
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=20141013212157.4e68147c@notabene.brown \
--to=neilb@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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