[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <527BE7FA.90904@oracle.com>
Date: Thu, 07 Nov 2013 13:20:26 -0600
From: Dave Kleikamp <dave.kleikamp@...cle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Jens Axboe <axboe@...nel.dk>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, Zach Brown <zab@...bo.net>,
Kent Overstreet <kmo@...erainc.com>,
Olof Johansson <olof@...om.net>
Subject: Re: linux-next: manual merge of the block tree with the tree
On 11/02/2013 03:50 PM, Dave Kleikamp wrote:
> On 11/01/2013 03:53 PM, Jens Axboe wrote:
>> So we've three immediate options:
>>
>> 1) You base it on top of the block tree
>> 2) I carry the loop updates
>> 3) You hand Stephen a merge patch for the resulting merge of the two
>
> Attached is a merge patch and the merged loop.c. I'm having problems
> with the loop driver with both the block and my tree. I'll continue to
> look at that, but everything should build cleanly with this.
Looking back, I obviously rushed the last patch out. This merge patch,
and the resulting loop.c, fix my problem. My code is working with Jens'
block tree now.
Jens,
I ended up replacing a call to bio_iovec_idx() with __bvec_iter_bvec()
since the former was removed. It's not very elegant, but it works. I'm
open to suggestions on a cleaner fix, but it can wait until one or both
of these trees is merged.
I'll be out next week away from internet access, so I'm looking at the
later half of the merge window.
Thanks,
Shaggy
View attachment "loop.c-merge2.patch" of type "text/x-patch" (3940 bytes)
View attachment "loop.c" of type "text/x-csrc" (50305 bytes)
Powered by blists - more mailing lists