From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Nicolin Chen <b42378@freescale.com>
Subject: linux-next: build failure after merge of the final tree (sound tree related)
Date: Tue, 29 Oct 2013 01:42:34 +1100 [thread overview]
Message-ID: <20131029014234.fa29fdc685dbd73934cf1768@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
Hi all,
After merging the final tree, today's linux-next build (i386 defconfig)
failed like this:
sound/built-in.o: In function `snd_free_dev_iram':
(.text+0x17028): undefined reference to `gen_pool_free'
Presumably caused by commit 055032142c42 ("ALSA: Add SoC on-chip internal
ram support for DMA buffer allocation") from the sound tree.
I have left this broken for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-10-28 14:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 14:42 Stephen Rothwell [this message]
2013-10-28 15:14 ` linux-next: build failure after merge of the final tree (sound tree related) Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2012-10-18 3:16 Stephen Rothwell
2012-10-18 6:18 ` Takashi Iwai
2012-08-24 7:20 Stephen Rothwell
2012-08-25 13:42 ` Takashi Iwai
2012-03-14 7:05 Stephen Rothwell
2012-03-14 7:22 ` Takashi Iwai
2011-11-01 9:24 Stephen Rothwell
2011-11-01 9:48 ` Takashi Iwai
2011-06-28 6:50 Stephen Rothwell
2011-06-28 6:57 ` Takashi Iwai
2011-06-14 6:03 Stephen Rothwell
2011-06-14 6:19 ` Takashi Iwai
2011-03-16 6:39 Stephen Rothwell
2011-03-16 6:49 ` Takashi Iwai
2011-01-11 2:20 Stephen Rothwell
2011-01-11 6:40 ` Takashi Iwai
2010-09-21 6:40 Stephen Rothwell
2010-09-21 8:02 ` Takashi Iwai
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=20131029014234.fa29fdc685dbd73934cf1768@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=b42378@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tiwai@suse.de \
/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).