From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lrg@slimlogic.co.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Zeng Zhaoming <zhaoming.zeng@freescale.com>
Subject: Re: linux-next: build failure after merge of the sound and sound-asoc trees
Date: Mon, 28 Feb 2011 14:34:18 +0000 [thread overview]
Message-ID: <20110228143418.GB13869@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110228141528.00fc4ab4.sfr@canb.auug.org.au>
On Mon, Feb 28, 2011 at 02:15:28PM +1100, Stephen Rothwell wrote:
> After merging the sound tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
I've applied a fix for this from Zjaoming.
next prev parent reply other threads:[~2011-02-28 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 3:15 linux-next: build failure after merge of the sound and sound-asoc trees Stephen Rothwell
2011-02-28 14:34 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-24 3:39 Stephen Rothwell
2012-09-24 7:48 ` Takashi Iwai
2012-09-24 7:52 ` Peter Ujfalusi
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=20110228143418.GB13869@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
--cc=zhaoming.zeng@freescale.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;
as well as URLs for NNTP newsgroup(s).