From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: testing (Was: Re: linux-next: scsi-post-merge tree build failure)
Date: Tue, 23 Dec 2008 11:19:35 +1100 [thread overview]
Message-ID: <1229991575.4360.31.camel@pasglop> (raw)
In-Reply-To: <20081223100456.bb556b19.sfr@canb.auug.org.au>
On Tue, 2008-12-23 at 10:04 +1100, Stephen Rothwell wrote:
> So, why is this series in powerpc/next at all if some of the modified
> files haven't even been compiled?
Because nobody spotted the problem while the series was out for review ?
> A simple ppc44x_defconfig build of the
> powerpc/next tree fails - which I would have thought would be part of the
> testing since KVM is only implemented for 44x on powerpc.
>
> (Sorry, I am annoyed - it was late when I finally found this build
> failure on top of everything else.)
I have about 3 44x configs in my build tests. KVM happens not to be
enabled in any of them :-( I'll add this ppc4xx_defconfig to the lot, I
didn't know it existed in fact.
Cheers,
Ben.
next prev parent reply other threads:[~2008-12-23 0:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 14:25 linux-next: scsi-post-merge tree build failure Stephen Rothwell
2008-12-22 14:51 ` Stephen Rothwell
2008-12-22 20:56 ` Benjamin Herrenschmidt
2008-12-22 23:04 ` testing (Was: Re: linux-next: scsi-post-merge tree build failure) Stephen Rothwell
2008-12-23 0:19 ` Benjamin Herrenschmidt [this message]
2008-12-23 1:52 ` Josh Boyer
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=1229991575.4360.31.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=hollisb@us.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).