From: Sam Ravnborg <sam@ravnborg.org>
To: Alex Chiang <achiang@hp.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [git pull] PCI changes for 2.6.30
Date: Mon, 6 Apr 2009 21:16:36 +0200 [thread overview]
Message-ID: <20090406191636.GA2366@uranus.ravnborg.org> (raw)
In-Reply-To: <20090406151931.GB25005@ldl.fc.hp.com>
On Mon, Apr 06, 2009 at 09:19:31AM -0600, Alex Chiang wrote:
> * Sam Ravnborg <sam@ravnborg.org>:
> > >
> > > Reading through Documentation/PCI/pci.txt says that under
> > > CONFIG_HOTPLUG, __devinit should be a nop?
> > The documentation is not up-to-date in this respect.
> >
> > Annotating a function __devinit will no matter the configuration
> > locate the code in a section named .devinit.text
>
> Ok, I'll update the documentation.
>
> > We then postprocess this section for illegal references using modpost.
> >
> > The PCI_HOTPLUG code has often been troublesome with respect to these checks
> > as this code is only relevant if CONFIG_HOTPLUG is enabled
> > and will often not even be included in the kernel if not enabled.
> > This is true for pci_rescan_bus() for example.
> >
> > And we would like to export these symbols too. But we do not allow exported
> > symbols to be annotated __devinit as this code will be blown away in some configurations.
> >
> > So the correct solution which you also used in your patch is to tell
> > modpost to ignore references to *init sections from this specific funtion
> > as they are OK.
>
> Does this count as an Acked-by?
If this is not too late - yes.
Sam
next prev parent reply other threads:[~2009-04-06 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 19:13 [git pull] PCI changes for 2.6.30 Jesse Barnes
2009-04-01 17:01 ` Linus Torvalds
2009-04-01 17:13 ` Jesse Barnes
2009-04-01 18:37 ` Alex Chiang
2009-04-01 19:12 ` Sam Ravnborg
2009-04-01 22:23 ` Alex Chiang
2009-04-05 19:34 ` Sam Ravnborg
2009-04-06 15:19 ` Alex Chiang
2009-04-06 19:16 ` Sam Ravnborg [this message]
2009-04-02 0:24 ` Alex Chiang
2009-04-06 18:46 ` Jesse Barnes
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=20090406191636.GA2366@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=achiang@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.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