From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (sound-asoc tree related)
Date: Fri, 19 Jul 2013 11:02:37 +0100 [thread overview]
Message-ID: <20130719100237.GC9858@sirena.org.uk> (raw)
In-Reply-To: <20130719135253.2689f6c0e42838f330b60df9@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
On Fri, Jul 19, 2013 at 01:52:53PM +1000, Stephen Rothwell wrote:
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
What goes into the final tree that might cause such breakage that didn't
appear in the earlier merges or is this additional testing that isn't
performed on the earlier merges?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-19 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 3:52 linux-next: build failure after merge of the final tree (sound-asoc tree related) Stephen Rothwell
2013-07-19 10:02 ` Mark Brown [this message]
2013-07-22 0:05 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2014-02-19 5:30 Stephen Rothwell
2013-12-10 4:02 Stephen Rothwell
2013-12-10 12:22 ` Mark Brown
2013-12-10 12:38 ` Mark Brown
2013-07-23 4:06 Stephen Rothwell
2011-12-17 4:34 Stephen Rothwell
2011-12-02 3:38 Stephen Rothwell
2011-12-02 10:53 ` Mark Brown
2011-12-02 10:55 ` Mark Brown
2011-09-22 8:44 Stephen Rothwell
2011-09-22 10:23 ` Mark Brown
2011-08-17 4:21 Stephen Rothwell
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=20130719100237.GC9858@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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.