From: Takashi Iwai <tiwai@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Mark_H_Johnson@raytheon.com, Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>,
perex@suse.cz, alsa-devel@alsa-project.org
Subject: Re: 2.6.10-mm1: ALSA ac97 compile error with CONFIG_PM=n
Date: Tue, 04 Jan 2005 20:16:44 +0100 [thread overview]
Message-ID: <s5hoeg5f1ib.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050104001130.GT2980@stusta.de>
At Tue, 4 Jan 2005 01:11:30 +0100,
Adrian Bunk wrote:
>
> On Mon, Jan 03, 2005 at 05:07:08PM -0600, Mark_H_Johnson@raytheon.com wrote:
> > I was looking to compare RT latency between this kernel and the latest from
> > Ingo and I had the following warnings / errors building 2.6.10-mm1:
> >
> > [no apparent compile / link errors]
> > *** Warning: "snd_ac97_restore_iec958" [sound/pci/ac97/snd-ac97-codec.ko]
> > undefined!
> > *** Warning: "snd_ac97_restore_status" [sound/pci/ac97/snd-ac97-codec.ko]
> > undefined!
> >...
> > To fix this, should I just add the EXPORT_SYMBOL lines for these symbols
> > snd_ac97_restore_status snd_ac97_restore_iec958
> > or is something more needed?
>
> That's not the problem, since function and definition are in the same
> module.
>
> You didn't send your .config, but looking at the code it seems
> CONFIG_PM=n was the culprit.
Yes, it's because of lack of #ifdef CONFIG_PM in ac97_patch.c.
It was already fixed in the linux-sound bk tree.
Takashi
next prev parent reply other threads:[~2005-01-04 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 23:07 2.6.10-mm1 Mark_H_Johnson
2005-01-03 23:15 ` 2.6.10-mm1 Andrew Morton
2005-01-04 0:11 ` 2.6.10-mm1: ALSA ac97 compile error with CONFIG_PM=n Adrian Bunk
2005-01-04 19:16 ` Takashi Iwai [this message]
2005-01-04 0:15 ` [2.6 patch] add missing dependencies on MTD_PARTITIONS (fwd) Adrian Bunk
2005-01-04 17:01 2.6.10-mm1: ALSA ac97 compile error with CONFIG_PM=n Mark_H_Johnson
2005-01-04 19:25 Mark_H_Johnson
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=s5hoeg5f1ib.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=Mark_H_Johnson@raytheon.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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).