From: Takashi Iwai <tiwai@suse•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Mark Brown <broonie@opensource•wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic•co.uk>
Subject: Re: linux-next: build failure after merge of the sound tree
Date: Thu, 23 Sep 2010 08:04:45 +0200 [thread overview]
Message-ID: <s5haan9ngg2.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100923124445.a2b5de42.sfr@canb.auug.org.au>
At Thu, 23 Sep 2010 12:44:45 +1000,
Stephen Rothwell wrote:
>
> Hi Takashi,
>
> After merging the sound tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> sound/soc/soc-cache.c: In function 'snd_soc_8_16_write':
> sound/soc/soc-cache.c:207: error: 'struct snd_soc_codec' has no member named 'reg_cache_size'
>
> Caused by commit 0077ca0b5c986477e33451b797b6e7dc92a8bbc0 ("ASoC: Fix
> multi-componentism") which looks like it was fixing something that didn't
> need fixing (or maybe fixed it incorrectly)? This commit is not in the
> sound-asoc tree (but the commit it purports to be fixing is in both the
> sound and sound-asoc trees) ...
>
Ah, this was a quick fix for 2.6.36, but it needs to be reverted again
for 2.6.37. for-next branch contains 2.6.37 patches, thus it got
broken. I fixed now. Mark, could you pull topic/asoc branch on my tree?
Sorry for inconvenience.
Takashi
next prev parent reply other threads:[~2010-09-23 6:04 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 2:44 linux-next: build failure after merge of the sound tree Stephen Rothwell
2010-09-23 6:04 ` Takashi Iwai [this message]
2010-09-23 8:39 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2026-06-04 15:07 Mark Brown
2026-06-04 15:19 ` Takashi Iwai
2025-06-16 3:01 Stephen Rothwell
2025-06-16 5:29 ` Christophe Leroy
2025-02-12 1:09 Stephen Rothwell
2025-02-12 7:22 ` Takashi Iwai
2025-01-20 3:56 Stephen Rothwell
2025-01-20 7:42 ` Takashi Iwai
2024-10-11 2:10 Stephen Rothwell
2024-10-11 7:22 ` Takashi Iwai
2024-08-09 1:22 Stephen Rothwell
2024-08-09 7:43 ` Takashi Iwai
2023-08-18 3:12 Stephen Rothwell
2023-08-18 11:47 ` Takashi Iwai
2023-05-24 3:54 Stephen Rothwell
2023-05-24 7:14 ` Takashi Iwai
2022-07-15 12:44 Stephen Rothwell
2022-07-15 14:41 ` Takashi Iwai
2022-07-15 19:09 ` Andy Shevchenko
2021-10-18 0:38 Stephen Rothwell
2021-10-18 6:35 ` Takashi Iwai
2020-07-17 3:01 Stephen Rothwell
2020-07-17 5:33 ` Christoph Hellwig
2020-07-17 6:34 ` Takashi Iwai
2020-07-17 6:50 ` Christoph Hellwig
2020-07-17 6:54 ` Takashi Iwai
2019-08-09 2:54 Stephen Rothwell
2019-08-09 5:55 ` Takashi Iwai
2017-05-17 1:29 Stephen Rothwell
2017-05-17 5:30 ` Takashi Iwai
2011-09-23 2:49 Stephen Rothwell
2011-09-23 5:21 ` Takashi Iwai
2011-05-19 1:15 Stephen Rothwell
2010-06-24 3:03 Stephen Rothwell
2010-06-24 6:11 ` Takashi Iwai
2010-06-28 16:33 ` Daniel Mack
2010-06-01 2:30 Stephen Rothwell
2010-06-01 5:47 ` Takashi Iwai
2010-04-07 3:39 Stephen Rothwell
2010-04-07 6:06 ` Takashi Iwai
2010-04-07 7:16 ` 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=s5haan9ngg2.wl%tiwai@suse.de \
--to=tiwai@suse$(echo .)de \
--cc=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lrg@slimlogic$(echo .)co.uk \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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