linux-kernel - Re: linux-next: build failure after merge of the sound tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Sep 2010 08:04:45 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...mlogic.co.uk>
Subject: Re: linux-next: build failure after merge of the sound tree

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/