[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq163fga654.fsf@sermon.lab.mkp.net>
Date: Mon, 01 Jun 2009 01:13:11 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Jens Axboe <jens.axboe@...cle.com>, Neil Brown <neilb@...e.de>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
raz ben yehuda <raziebe@...il.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Subject: Re: linux-next: md tree build failure
>>>>> "Stephen" == Stephen Rothwell <sfr@...b.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?
--
Martin K. Petersen Oracle Linux Engineering
--
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