From: Randy Dunlap <randy.dunlap@oracle.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>,
perex@suse.cz, sam@ravnborg.org
Subject: Re: [PATCH -mm] ALSA portman2x4 section mismatch
Date: Thu, 28 Jun 2007 10:24:38 -0700 [thread overview]
Message-ID: <20070628102438.cafa1b41.randy.dunlap@oracle.com> (raw)
In-Reply-To: <s5h3b0dg1fr.wl%tiwai@suse.de>
On Wed, 27 Jun 2007 12:02:32 +0200 Takashi Iwai wrote:
> At Tue, 26 Jun 2007 15:30:13 -0700,
> Randy Dunlap wrote:
> >
> > From: Randy Dunlap <randy.dunlap@oracle.com>
> >
> > FIx section mismatch when CONFIG_HOTPLUG=n:
> >
> > WARNING: sound/built-in.o(.exit.text+0x271): Section mismatch: reference to .init.text:snd_p
> > ortman_unregister_all (between 'snd_portman_module_exit' and 'alsa_mpu401_uart_exit')
> >
> > Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
>
> I applied it to ALSA tree now because it's the simplest way to fix
> this warning. But, I'm still wondering whether it was really wrong.
>
> The function snd_portmap_unregister_all() is called both from the
> module init and exit functions. Would the module_exit function be
> called even CONFIG_MODULE=n ?
No, it's not called when the driver is built-in.
> If not, __init_or_module should be
> correct since the function is called only from module_init.
[adding Sam to cc:]
I see. So to try to summarize:
When CONFIG_MODULES=n, __exit functions can be allowed to reference
__init functions since the __init functions won't be called because
the __exit functions are not invoked.
Does that sound correct? Can & should modpost add this knowledge?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-06-28 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 22:30 [PATCH -mm] ALSA portman2x4 section mismatch Randy Dunlap
2007-06-27 10:02 ` Takashi Iwai
2007-06-28 17:24 ` Randy Dunlap [this message]
2007-06-28 18:15 ` Sam Ravnborg
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=20070628102438.cafa1b41.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=sam@ravnborg.org \
--cc=tiwai@suse.de \
/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