From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "KOCHI, Takayoshi" <t-kouchi@mvf.biglobe.ne.jp>,
jung-ik.lee@intel.com, tony.luck@intel.com,
pcihpd-discuss@lists.sourceforge.net, linux-ia64@linuxia64.org,
linux-kernel@vger.kernel.org
Subject: Re: PCI Hotplug Drivers for 2.5
Date: Thu, 24 Oct 2002 09:54:11 -0700 [thread overview]
Message-ID: <20021024165411.GG22654@kroah.com> (raw)
In-Reply-To: <3DB80919.5030500@pobox.com>
On Thu, Oct 24, 2002 at 10:52:09AM -0400, Jeff Garzik wrote:
> Greg KH wrote:
> >I think we now all agree that resource management should move into a
> >place where it can be shared by all pci hotplug drivers, right?
> >
> >If so, anyone want to propose some common code?
>
>
> drivers/pci/setup* is not enough?
>
> I am surprised that anything needed to be added here...
There was some reason that code would not work out when I looked at it
over a year ago. But I don't remember why, so I'll go look at it again,
thanks for pointing it out.
greg k-h
next prev parent reply other threads:[~2002-10-24 16:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 4:33 PCI Hotplug Drivers for 2.5 Lee, Jung-Ik
2002-10-24 5:10 ` Greg KH
2002-10-24 5:59 ` KOCHI, Takayoshi
2002-10-24 6:12 ` Greg KH
2002-10-24 11:49 ` [Linux-ia64] " Matthew Wilcox
2002-10-24 14:52 ` Jeff Garzik
2002-10-24 16:54 ` Greg KH [this message]
2002-10-24 17:44 ` [Pcihpd-discuss] " Scott Murray
2002-10-24 21:49 ` Greg KH
2002-10-24 22:22 ` Scott Murray
2002-10-25 15:37 ` Ivan Kokshaysky
2002-10-25 22:02 ` Scott Murray
2002-10-25 22:25 ` Russell King
2002-10-26 23:36 ` Scott Murray
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 16:24 Lee, Jung-Ik
2002-10-24 16:46 ` Greg KH
2002-10-24 17:40 ` Lee, Jung-Ik
2002-10-24 22:06 ` Greg KH
2002-10-24 17:39 ` KOCHI, Takayoshi
2002-10-24 17:52 ` Jeff Garzik
2002-10-24 16:37 Lee, Jung-Ik
2002-10-24 18:39 Lee, Jung-Ik
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=20021024165411.GG22654@kroah.com \
--to=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=jung-ik.lee@intel.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=t-kouchi@mvf.biglobe.ne.jp \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).