From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Bas Vermeulen <bas.vermeulen@novero.com>
Subject: Re: linux-next: build failure after merge of the final tree (sound-asoc tree related)
Date: Thu, 22 Sep 2011 11:23:59 +0100 [thread overview]
Message-ID: <20110922102358.GA5173@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110922184418.63db26a381abe00d73eb9c36@canb.auug.org.au>
On Thu, Sep 22, 2011 at 06:44:18PM +1000, Stephen Rothwell wrote:
> sound/soc/codecs/88pm860x-codec.c: In function 'pm860x_set_bias_level':
> sound/soc/codecs/88pm860x-codec.c:1184:4: error: implicit declaration of function 'udelay'
> Caused by commit 548aae8cc497 ("ASoC: 88pm860x-codec - reset the codec
> correctly") from the sound-asoc tree. Forgot an include file.
Well, arguably that's all the header file reorganizations causing things
to break when merged. But anyway it's fixed now.
next prev parent reply other threads:[~2011-09-22 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 8:44 linux-next: build failure after merge of the final tree (sound-asoc tree related) Stephen Rothwell
2011-09-22 10:23 ` Mark Brown [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
2013-07-19 3:52 Stephen Rothwell
2013-07-19 10:02 ` Mark Brown
2013-07-22 0:05 ` 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-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=20110922102358.GA5173@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=bas.vermeulen@novero.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--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).