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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <s5hzkvbfrsd.wl%tiwai@suse.de>
Date:	Tue, 21 Sep 2010 10:02:26 +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
Subject: Re: linux-next: build failure after merge of the final tree (sound tree related)

At Tue, 21 Sep 2010 16:40:25 +1000,
Stephen Rothwell wrote:
> 
> Hi ,
> 
> After merging the final tree, today's linux-next build (i386 defconfig)
> failed like this:
> 
> sound/pci/hda/patch_realtek.c: In function 'alc_resume':
> sound/pci/hda/patch_realtek.c:4131: error: 'struct hda_codec_ops' has no member named 'check_power_status'
> sound/pci/hda/patch_realtek.c:4132: error: 'struct hda_codec_ops' has no member named 'check_power_status'
> sound/pci/hda/patch_realtek.c: In function 'alc269_resume':
> sound/pci/hda/patch_realtek.c:14706: error: 'struct hda_codec_ops' has no member named 'check_power_status'
> sound/pci/hda/patch_realtek.c:14707: error: 'struct hda_codec_ops' has no member named 'check_power_status'
> 
> Caused by commit 0ec33d1f952934ea3251cefc6d108b47818eedd0 ("ALSA: hda -
> Refactor ALC269 power-ups/downs in PM callbacks").  I have reverted that
> commit for today.

Thanks.  This should have been fixed now on sound git tree.


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/