From: Greg KH <greg@kroah.com>
To: Scott Murray <scottm@somanetworks.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: PCI hotplug resource reservation
Date: Thu, 8 Aug 2002 10:06:11 -0700 [thread overview]
Message-ID: <20020808170611.GA21821@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0208061714560.16357-100000@rancor.yyz.somanetworks.com>
On Tue, Aug 06, 2002 at 05:16:30PM -0400, Scott Murray wrote:
> I've been using this for several weeks now, and it allows me to hot
> insert new devices quite well. However, my goal for my CompactPCI work
> is to get it into the mainline kernel so people can add drivers for
> other boards and chassis on top of it. If this resource reservation
> scheme is too distasteful, or there is indeed a "cleaner" way, I'd
> really like comments or suggestions before I push on much further.
Hm, now that it looks like this is going to be necessary for cPCI
hotplug drivers, could you make up a 2.5 version of it?
The code should only be compiled in if CONFIG_HOTPLUG_PCI_CPCI is
enabled, and hopefully with the splitup of the PCI code in the 2.5 tree,
you should be able to contain it to one file, much like this patch has.
One small comment:
> @@ -2031,6 +2031,10 @@
> struct pci_dev *dev;
>
> pcibios_init();
> +
> +#ifdef CONFIG_HOTPLUG_PCI
> + pci_hp_reserve_resources();
> +#endif
Move this #ifdef to a header file file, so it doesn't show up in the .c
file.
thanks,
greg k-h
next prev parent reply other threads:[~2002-08-08 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 21:16 RFC: PCI hotplug resource reservation Scott Murray
2002-08-07 11:38 ` David Woodhouse
2002-08-07 13:44 ` Scott Murray
2002-08-07 13:48 ` David Woodhouse
2002-08-07 19:01 ` Scott Murray
2002-08-07 19:02 ` David Woodhouse
2002-08-07 19:35 ` Scott Murray
2002-08-08 7:13 ` David Woodhouse
2002-08-08 17:44 ` Scott Murray
2002-08-08 19:44 ` David Woodhouse
2002-08-08 21:59 ` Scott Murray
2002-08-08 17:06 ` Greg KH [this message]
2002-08-08 17:36 ` Scott Murray
2002-08-08 18:19 ` Greg KH
2002-08-08 18:56 ` Scott Murray
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=20020808170611.GA21821@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scottm@somanetworks.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