linux-kernel - Re: linux-next: build failure after merge of the final tree (sound tree related)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <s5hbohz84wi.wl%tiwai@suse.de>
Date:	Sat, 25 Aug 2012 15:42:05 +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,
	Mengdong Lin <mengdong.lin@...el.com>
Subject: Re: linux-next: build failure after merge of the final tree (sound tree related)

At Fri, 24 Aug 2012 17:20:18 +1000,
Stephen Rothwell wrote:
> 
> Hi all,
> 
> After merging the final tree, today's linux-next build (i386 defconfig)
> failed like this:
> 
> sound/pci/hda/hda_codec.c: In function 'snd_hda_codec_new':
> sound/pci/hda/hda_codec.c:1323:7: error: 'struct hda_codec' has no member named 'd3_stop_clk'
> sound/pci/hda/hda_codec.c:1326:12: error: 'struct hda_codec' has no member named 'd3_stop_clk'
> sound/pci/hda/hda_codec.c: In function 'hda_set_power_state':
> sound/pci/hda/hda_codec.c:3547:7: error: 'struct hda_codec' has no member named 'd3_stop_clk_ok'
> sound/pci/hda/hda_codec.c:3573:11: error: 'struct hda_codec' has no member named 'd3_stop_clk'
> sound/pci/hda/hda_codec.c:3574:8: error: 'struct hda_codec' has no member named 'd3_stop_clk_ok'
> 
> Caused by commit b8dfc4624162 ("ALSA: hda - add runtime PM support").
> CONFIG_SND_HDA_POWER_SAVE is not set for this build.
> 
> I have reverted that commit for today.

This should have been fixed now.  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/