From: Takashi Iwai <tiwai@suse.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: linux-next: Tree for Mar 16 (sound)
Date: Fri, 16 Mar 2012 16:08:55 +0100 [thread overview]
Message-ID: <s5haa3gtwfs.wl%tiwai@suse.de> (raw)
In-Reply-To: <4F6355B2.5080909@xenotime.net>
At Fri, 16 Mar 2012 08:01:06 -0700,
Randy Dunlap wrote:
>
> [1 <text/plain; UTF-8 (7bit)>]
> On 03/16/2012 12:39 AM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20120315:
> >
> > The sound tree lost its build failure.
>
>
>
>
> on i386:
>
> sound/pci/hda/patch_sigmatel.c: In function 'patch_stac92hd83xxx':
> sound/pci/hda/patch_sigmatel.c:5589:6: error: 'stac92xx_set_power_state' undeclared (first use in this function)
> sound/pci/hda/patch_sigmatel.c:5589:6: note: each undeclared identifier is reported only once for each function it appears in
> sound/pci/hda/patch_sigmatel.c:5591:19: error: 'struct hda_codec_ops' has no member named 'pre_resume'
> sound/pci/hda/patch_sigmatel.c:5591:33: error: 'stac92xx_pre_resume' undeclared (first use in this function)
> /home/rddunlap/lnx/next/linux-next-20120316/sound/pci/hda/patch_sigmatel.c: In function 'patch_stac92hd71bxx':
> sound/pci/hda/patch_sigmatel.c:5896:6: error: 'stac92xx_set_power_state' undeclared (first use in this function)
> sound/pci/hda/patch_sigmatel.c:5898:19: error: 'struct hda_codec_ops' has no member named 'pre_resume'
> sound/pci/hda/patch_sigmatel.c:5898:33: error: 'stac92xx_pre_resume' undeclared (first use in this function)
I seem to have overlooked the case CONFIG_PM=n.
Fixed now.
thanks,
Takashi
prev parent reply other threads:[~2012-03-16 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 7:39 linux-next: Tree for Mar 16 Stephen Rothwell
2012-03-16 15:01 ` linux-next: Tree for Mar 16 (sound) Randy Dunlap
2012-03-16 15:08 ` Takashi Iwai [this message]
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=s5haa3gtwfs.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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).