From: "Martin K. Petersen" <martin.petersen@oracle•com>
To: Jens Axboe <jens.axboe@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
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, 25 May 2009 07:44:14 -0400 [thread overview]
Message-ID: <yq17i05flv5.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20090525061552.GH11363@kernel.dk> (Jens Axboe's message of "Mon, 25 May 2009 08:15:52 +0200")
>>>>> "Jens" == Jens Axboe <jens.axboe@oracle•com> writes:
Jens> Martin, this is starting to look like a disaster :-(
Yeah. I guess you should have pushed the accessors first and let that
patch steep for a while before applying the rest of the kit :|
It's just super bad timing that both Neil and Alasdair had patches to
their respective hardsect size areas right now. Neither tree has been
touched in that department for ages...
*sigh*
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2009-05-25 11:44 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 [this message]
2009-06-01 4:42 ` Stephen Rothwell
2009-06-01 5:13 ` Martin K. Petersen
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=yq17i05flv5.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle$(echo .)com \
--cc=jens.axboe@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=neilb@suse$(echo .)de \
--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