From: Thierry Reding <thierry.reding@avionic-design.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: David Daney <ddaney.cavm@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-pci@vger.kernel.org, linux-mips <linux-mips@linux-mips.org>
Subject: Re: PCI Section mismatch error in linux-next.
Date: Fri, 17 Aug 2012 23:07:18 +0200 [thread overview]
Message-ID: <20120817210718.GA14842@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <20120817204839.GA2017@avionic-0098.mockup.avionic-design.de>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Fri, Aug 17, 2012 at 10:48:39PM +0200, Thierry Reding wrote:
> On Fri, Aug 17, 2012 at 02:39:34PM -0600, Bjorn Helgaas wrote:
[...]
> > Well, maybe you just need to turn on CONFIG_HOTPLUG. How would that
> > affect you? I think we would still have to change some __inits to
> > __devinit, including pcibios_update_irq(), but it might be more
> > manageable.
>
> You said that depending on HOTPLUG wouldn't be enough because it would
> exclude reenumeration at runtime if HOTPLUG wasn't defined. Also it is
> theoretically possible to build a kernel without HOTPLUG but have the
> enumeration start after init because of deferred probing. Those cases
> won't work if we keep __init or __devinit respectively, right?
Another possibility would be to make PCI select HOTPLUG or depend on it.
That way it would be made sure that __devinit wouldn't cause all the
functions to be discarded after init.
Also, using PCI without HOTPLUG is sort of contradictory.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-17 21:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 17:36 PCI Section mismatch error in linux-next David Daney
2012-08-17 17:44 ` Bjorn Helgaas
2012-08-17 18:29 ` Thierry Reding
2012-08-17 19:32 ` Bjorn Helgaas
2012-08-17 20:07 ` Thierry Reding
2012-08-17 20:39 ` Bjorn Helgaas
2012-08-17 20:48 ` Thierry Reding
2012-08-17 21:06 ` Bjorn Helgaas
2012-08-17 21:22 ` Thierry Reding
2012-08-17 21:07 ` Thierry Reding [this message]
2012-08-17 21:25 ` Bjorn Helgaas
2012-08-17 21:32 ` Thierry Reding
2012-08-17 21:46 ` Bjorn Helgaas
2012-08-17 21:46 ` Bjorn Helgaas
2012-08-20 5:30 ` Greg KH
2012-08-20 7:16 ` Thierry Reding
2012-08-21 14:32 ` Geert Uytterhoeven
2012-08-21 17:04 ` Ralf Baechle
2012-08-21 18:15 ` Geert Uytterhoeven
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=20120817210718.GA14842@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=bhelgaas@google.com \
--cc=ddaney.cavm@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-pci@vger.kernel.org \
--cc=ralf@linux-mips.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