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, linux-kernel@vger.kernel.org,
Ondrej Zary <linux@rainbow-software.org>,
Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH -next] sound: ice1712 build errors
Date: Tue, 23 Oct 2012 20:33:49 +0200 [thread overview]
Message-ID: <s5h3915hwc2.wl%tiwai@suse.de> (raw)
In-Reply-To: <5086D518.7050606@xenotime.net>
At Tue, 23 Oct 2012 10:34:16 -0700,
Randy Dunlap wrote:
>
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Fix build errors by using correct kconfig symbol name:
>
> sound/pci/ice1712/psc724.c:417:5: error: 'struct snd_ice1712' has no member named 'pm_resume'
> sound/pci/ice1712/psc724.c:418:5: error: 'struct snd_ice1712' has no member named 'pm_suspend_enabled'
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> Cc: Ondrej Zary <linux@rainbow-software.org>
> Cc: Jaroslav Kysela <perex@perex.cz>
> Cc: Takashi Iwai <tiwai@suse.de>
> Cc: alsa-devel@alsa-project.org
Thanks, I applied with one more replacement of #ifdef CONFIG_PM with
CONFIG_PM_SLEEP in the same file.
Takashi
> ---
> sound/pci/ice1712/psc724.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20121023.orig/sound/pci/ice1712/psc724.c
> +++ linux-next-20121023/sound/pci/ice1712/psc724.c
> @@ -413,7 +413,7 @@ static int __devinit psc724_init(struct
> snd_wm8776_init(&spec->wm8776);
> spec->wm8766.ops.write = psc724_wm8766_write;
> spec->wm8766.card = ice->card;
> -#ifdef CONFIG_PM
> +#ifdef CONFIG_PM_SLEEP
> ice->pm_resume = psc724_resume;
> ice->pm_suspend_enabled = 1;
> #endif
>
prev parent reply other threads:[~2012-10-23 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 4:19 linux-next: Tree for Oct 23 Stephen Rothwell
2012-10-23 17:34 ` [PATCH -next] sound: ice1712 build errors Randy Dunlap
2012-10-23 18:01 ` Ondrej Zary
2012-10-23 18:33 ` 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=s5h3915hwc2.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=linux@rainbow-software.org \
--cc=perex@perex.cz \
--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).