From: Dave Kleikamp <dave.kleikamp@oracle•com>
To: Christoph Hellwig <hch@infradead•org>,
Stephen Rothwell <sfr@canb•auug.org.au>
Cc: LKML <linux-kernel@vger•kernel.org>,
linux-fsdevel@vger•kernel.org,
Andrew Morton <akpm@linux-foundation•org>,
"Maxim V. Patlasov" <mpatlasov@parallels•com>,
Zach Brown <zab@zabbo•net>,
Linux-Next <linux-next@vger•kernel.org>
Subject: Re: [PATCH V8 00/33] loop: Issue O_DIRECT aio using bio_vec
Date: Tue, 20 Aug 2013 14:13:15 -0500 [thread overview]
Message-ID: <5213BFCB.3010503@oracle.com> (raw)
In-Reply-To: <20130820130056.GA9652@infradead.org>
Stephen,
Would you be willing to pick up
git://github.com/kleikamp/linux-shaggy.git for-next
into linux-next?
There will be some unclean merges, and I can send you updated patches
created against your latest tree. I'm not exactly sure of your process
wrt cleaning up merges, but I guess they would help.
Thanks,
Shaggy
On 08/20/2013 08:00 AM, Christoph Hellwig wrote:
> As I've seen very few replies to this: how do we ensure this gets
> picked up for the 3.12 merge window? The series has been a reposted
> a few times without complaints or major changes, but the ball still
> doesn't seem to get rolling.
>
> I'd really like to do some ecryptfs and scsi target work that is going
> to rely on this soon.
>
next parent reply other threads:[~2013-08-20 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1374774659-13121-1-git-send-email-dave.kleikamp@oracle.com>
[not found] ` <20130820130056.GA9652@infradead.org>
2013-08-20 19:13 ` Dave Kleikamp [this message]
2013-08-21 0:14 ` [PATCH V8 00/33] loop: Issue O_DIRECT aio using bio_vec Stephen Rothwell
2013-08-21 5:35 ` Sedat Dilek
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=5213BFCB.3010503@oracle.com \
--to=dave.kleikamp@oracle$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=hch@infradead$(echo .)org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mpatlasov@parallels$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=zab@zabbo$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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