[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1204640722.5783.10.camel@homer.simson.net>
Date: Tue, 04 Mar 2008 15:25:22 +0100
From: Mike Galbraith <efault@....de>
To: Jens Axboe <jens.axboe@...cle.com>
Cc: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>, htejun@...il.com,
tomof@....org, James.Bottomley@...senPartnership.com,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org,
jgarzik@...ox.com, bzolnier@...il.com
Subject: Re: [PATCH] block: fix residual byte count handling
On Tue, 2008-03-04 at 14:03 +0100, Jens Axboe wrote:
> Re-read my original mail! It states that you should just pull:
>
> git://git.kernel.dk/linux-2.6-block.git for-linus
>
> into your linus branch, or just create a test branch off linus' master
> and pull into that. IOW, it's the for-linus branch that you should pull,
> nothing else.
Well, I had a good reason. You know how to un-pull, I know how to
un-remote to get back to pristine after I'm done testing... guaranteed
without whimpering pathetically on the git list ;-)
Anyway, I checked out the one with the big-fat-hint in it's name
(block-for-linus/for-linus).
Same error. Git this morning with patches...
restore_meaning_of_data_len.diff
seperate_out_padding_from_alignment.diff
...reverted restored me to the originally reported k3b error, nothing
new noted.
If I tested the wrong branch, whack me upside the head, and I'll follow
your pull destructions, and figure out how to un-pull later.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists