From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Vikas Chaudhary <vikas.chaudhary@qlogic.com>,
Karen Higgins <karen.higgins@qlogic.com>,
Ravi Anand <ravi.anand@qlogic.com>
Subject: Re: linux-next: build failure after merge of the final tree (scsi tree related)
Date: Wed, 28 Jul 2010 07:32:34 -0500 [thread overview]
Message-ID: <1280320354.30808.8.camel@mulgrave.site> (raw)
In-Reply-To: <20100728160530.da25fdb1.sfr@canb.auug.org.au>
On Wed, 2010-07-28 at 16:05 +1000, Stephen Rothwell wrote:
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
Yes, sorry. Already being discussed in this thread ... please follow
for resolution:
http://marc.info/?t=128025755400005
James
prev parent reply other threads:[~2010-07-28 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 6:05 linux-next: build failure after merge of the final tree (scsi tree related) Stephen Rothwell
2010-07-28 12:32 ` James Bottomley [this message]
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=1280320354.30808.8.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=karen.higgins@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ravi.anand@qlogic.com \
--cc=sfr@canb.auug.org.au \
--cc=vikas.chaudhary@qlogic.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox