From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>
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: Mon, 22 Jul 2013 10:05:50 +1000 [thread overview]
Message-ID: <20130722100550.553af77b06c5de6a2471a47b@canb.auug.org.au> (raw)
In-Reply-To: <20130719100237.GC9858@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
HI Mark,
On Fri, 19 Jul 2013 11:02:37 +0100 Mark Brown <broonie@kernel.org> wrote:
>
> 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?
From my daily release message:
"You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc,
sparc64 and arm defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary."
The powerpc allyesconfig catches quite a few build problems.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-22 0:06 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
2013-07-22 0:05 ` Stephen Rothwell [this message]
-- 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=20130722100550.553af77b06c5de6a2471a47b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).