From: Takashi Iwai <tiwai@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Karsten Keil <kkeil@suse.de>,
greg@kroah.com, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hisax fix usage of __init*
Date: Wed, 05 Jul 2006 17:08:09 +0200 [thread overview]
Message-ID: <s5h8xn8144m.wl%tiwai@suse.de> (raw)
In-Reply-To: <1152099459.3201.19.camel@laptopd505.fenrus.org>
At Wed, 05 Jul 2006 13:37:38 +0200,
Arjan van de Ven wrote:
>
> On Wed, 2006-07-05 at 13:23 +0200, Karsten Keil wrote:
> > diff --git a/drivers/isdn/hisax/config.c b/drivers/isdn/hisax/config.c
> > index 5333be5..e103503 100644
> > --- a/drivers/isdn/hisax/config.c
> > +++ b/drivers/isdn/hisax/config.c
> > @@ -1875,7 +1875,7 @@ static void EChannel_proc_rcv(struct his
> > #ifdef CONFIG_PCI
> > #include <linux/pci.h>
> >
> > -static struct pci_device_id hisax_pci_tbl[] __initdata = {
> > +static struct pci_device_id hisax_pci_tbl[] __devinitdata = {
> > #ifdef CONFIG_HISAX_FRITZPCI
> > {PCI_VENDOR_ID_AVM, PCI_DEVICE_ID_AVM_A1,
> > PCI_ANY_ID, PCI_ANY_ID},
> > #endif
> > diff --git a/drivers
>
> I think this bit is still buggy; afaik pci_device_id tables should not
> be of any kind of __init at all... CC'ing Greg just to make sure I'm not
> talking rubbish
I've been also debugging this since Andrew pointed me about a similar
bug (sound/pci/maestro3.c). I actually got section mismatch errors
when pci id table is defined with __devinitdata tag together with
CONFIG_HOTPLUG=n, either at compile time or at link time. So, my
conclusion is that no tags should be used for pci id table.
Interestingly, Documentation/pci.txt mentions that __devinitdata
_should_ be used:
> Tips:
> The module_init()/module_exit() functions (and all initialization
> functions called only from these) should be marked __init/exit.
> The struct pci_driver shouldn't be marked with any of these tags.
> The ID table array should be marked __devinitdata.
Takashi
next prev parent reply other threads:[~2006-07-05 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 11:23 Karsten Keil
2006-07-05 11:37 ` Arjan van de Ven
2006-07-05 15:08 ` Takashi Iwai [this message]
2006-07-06 19:11 ` Greg KH
2006-07-06 19:22 ` Andrew Morton
2006-07-06 19:38 ` Greg KH
2006-07-06 20:22 ` Randy.Dunlap
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=s5h8xn8144m.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®