From: Greg KH <greg@kroah.com>
To: "Lee, Jung-Ik" <jung-ik.lee@intel.com>
Cc: pcihpd-discuss@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Patch: 2.5.45 PCI Fixups for PCI HotPlug
Date: Sat, 2 Nov 2002 23:58:06 -0800 [thread overview]
Message-ID: <20021103075806.GF25821@kroah.com> (raw)
In-Reply-To: <72B3FD82E303D611BD0100508BB29735046DFF71@orsmsx102.jf.intel.com>
On Sat, Nov 02, 2002 at 04:56:58PM -0800, Lee, Jung-Ik wrote:
> Hi Greg,
>
> The following patch changes function scopes only but fixes kernel dump on
> Hot-Add of PCI bridge cards.
Applied, thanks.
Hm, in looking at this, I know the majority of people who want
CONFIG_HOTPLUG probably do not run with CONFIG_PCI_HOTPLUG as the
hardware's still quite rare. To force those people to keep around all
of the PCI quirks functions and tables after init happens, is a bit
cruel. I wonder if it's time to start having different subsystems
modify __devinit depending on their config variables.
Does this sound like a good idea? If so, I can probably knock up
something for the PCI code pretty easily (yes, I'll keep in mind CardBus
stuff, not all hotplug pci is on servers...)
__pci_devinit anyone? :)
thanks,
greg k-h
next prev parent reply other threads:[~2002-11-03 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 0:56 Patch: 2.5.45 PCI Fixups for PCI HotPlug Lee, Jung-Ik
2002-11-03 7:58 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-03 12:31 Adam J. Richter
2002-11-04 18:06 Lee, Jung-Ik
2002-11-04 18:23 Adam J. Richter
2002-11-04 19:05 ` Alan Cox
2002-11-04 20:29 Adam J. Richter
2002-11-04 20:44 ` Jeff Garzik
2002-11-05 13:01 ` Ivan Kokshaysky
2002-11-05 13:17 Adam J. Richter
2002-11-05 15:28 ` Ivan Kokshaysky
2002-11-06 0:14 Adam J. Richter
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=20021103075806.GF25821@kroah.com \
--to=greg@kroah.com \
--cc=jung-ik.lee@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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