From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jens Axboe <jens.axboe@oracle.com>, Neil Brown <neilb@suse.de>,
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, 01 Jun 2009 01:13:11 -0400 [thread overview]
Message-ID: <yq163fga654.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20090601144218.26810ec8.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 1 Jun 2009 14:42:18 +1000")
>>>>> "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?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2009-06-01 5:13 UTC|newest]
Thread overview: 17+ 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 [this message]
2009-06-01 5:33 ` NeilBrown
2009-06-01 5:33 ` NeilBrown
[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=yq163fga654.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=neilb@suse.de \
--cc=raziebe@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.