From: Prarit Bhargava <prarit@redhat.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: michael@tweakoz.com, alsa-devel@lists.sourceforge.net, perex@suse.cz
Subject: Re: [PATCH]: Fix __devinit and __devexit issues with sound drivers
Date: Wed, 14 Feb 2007 10:09:22 -0500 [thread overview]
Message-ID: <45D32622.8090503@redhat.com> (raw)
In-Reply-To: <s5hveibmhs4.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Fri, 9 Feb 2007 09:49:03 -0500,
> Prarit Bhargava wrote:
>
>> Fix __devinit and __devexit issues with sound drivers.
>>
>> Resolves MODPOST warnings similar to:
>>
>> WARNING: sound/drivers/snd-dummy.o - Section mismatch: reference to
>> .init.text:snd_dummy_probe from .data.rel.local between 'snd_dummy_driver' (at
>> offset 0x0) and 'snd_dummy_controls'
>> WARNING: sound/drivers/snd-mtpav.o - Section mismatch: reference to
>> .init.text:snd_mtpav_probe from .data.rel.local between 'snd_mtpav_driver' (at
>> offset 0x0) and 'snd_mtpav_input'
>> WARNING: sound/drivers/snd-virmidi.o - Section mismatch: reference to
>> .init.text:snd_virmidi_probe from .data.rel.local after 'snd_virmidi_driver' (at
>> offset 0x0)
>>
>> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
>>
>
>
Sorry for the late reply Takashi -- I got tied up with a few other things.
> Thanks for the patch. But I'm afraid we need to change more from
> __init* to __devinit*, i.e. the functions called from __devinit
> shouldn't be __init but also __deveinit (for example, some functions
> in sound/drivers/dummy.c should be __devinit too). Ditto for
> __initdata.
>
>
It's odd that MODPOST didn't kick out more warnings. I was relying on
it to complain about __init & __devinit collisions. I've ping'd a few
others to see if we can figure out why no further errors were output.
> Also, could you separate patches for sound/oss/* and others? We keep
> only ALSA stuff in our tree and it's not easy to apply the patches to
> old OSS drivers all together.
>
>
Sure -- new patcheset to follow.
P.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-02-14 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070209144903.22210.59758.sendpatchset@prarit.boston.redhat.com>
2007-02-09 16:12 ` [PATCH]: Fix __devinit and __devexit issues with sound drivers Takashi Iwai
2007-02-14 15:09 ` Prarit Bhargava [this message]
2007-02-14 15:23 ` Takashi Iwai
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=45D32622.8090503@redhat.com \
--to=prarit@redhat.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=michael@tweakoz.com \
--cc=perex@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.