From: "NeilBrown" <neilb@suse•de>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Jens Axboe <jens.axboe@oracle•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
raz ben yehuda <raziebe@gmail•com>,
"Martin K. Petersen" <martin.petersen@oracle•com>
Subject: Re: linux-next: md tree build failure
Date: Mon, 1 Jun 2009 15:33:07 +1000 (EST) [thread overview]
Message-ID: <39efa6d3788eec04b0bc86b02d988c8f.squirrel@neil.brown.name> (raw)
In-Reply-To: <yq163fga654.fsf@sermon.lab.mkp.net>
On Mon, June 1, 2009 3:13 pm, Martin K. Petersen wrote:
>>>>>> "Stephen" == Stephen Rothwell <sfr@canb•auug.org.au> writes:
>
>>> > Caused by commit e1defc4ff0cf57aca6c5e3ff99fa503f5943c1f1 ("block:
>>> > Do away with the notion of hardsect_size") from the block tree
>>> > interacting with commit 131e4477401ae76a9cbe8539e4b7819e04cfba36
>>> > ("md: raid0: chunk size check in raid0_run") from the md tree.
>
> Stephen> So, is anything happening about these? I still get these (and
> Stephen> the dm) build failures.
>
> There's a replacement DM patch kit brewing that will hopefully come your
> way shortly. It replaces the patches currently in Alasdair's tree.
> Mike sent the kit out for review last week and I'm currently testing it.
>
>
> I don't know what Neil's plans are. Neil: Do you want to rebase your
> tree, fix up the conflicting patches or how would you like to handle
> this?
I'm happy to rebase on something if you have a tree that doesn't have too
much more than the changes that are causing conflicts.
Then I'll fix my patches so they work on that tree.
What should I pull??
NeilBrown
next prev parent reply other threads:[~2009-06-01 5:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 5:33 linux-next: md tree build failure Stephen Rothwell
2009-05-25 6:15 ` Jens Axboe
2009-05-25 11:44 ` Martin K. Petersen
2009-06-01 4:42 ` Stephen Rothwell
2009-06-01 5:13 ` Martin K. Petersen
2009-06-01 5:33 ` NeilBrown [this message]
[not found] ` <yq1prdm6jn1.fsf@sermon.lab.mkp.net>
2009-06-04 4:06 ` Neil Brown
2009-06-04 4:17 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2009-03-11 5:27 Stephen Rothwell
2009-03-13 0:45 ` Neil Brown
2009-03-13 2:21 ` Stephen Rothwell
2009-03-10 5:47 Stephen Rothwell
2009-03-10 6:38 ` NeilBrown
2009-03-10 6:48 ` Stephen Rothwell
2008-10-15 9:09 Stephen Rothwell
2008-10-15 10:55 ` Neil Brown
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=39efa6d3788eec04b0bc86b02d988c8f.squirrel@neil.brown.name \
--to=neilb@suse$(echo .)de \
--cc=jens.axboe@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin.petersen@oracle$(echo .)com \
--cc=raziebe@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/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