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 11:19:32 -0700 [thread overview]
Message-ID: <20020808181931.GA22209@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0208081326480.26999-100000@rancor.yyz.somanetworks.com>
On Thu, Aug 08, 2002 at 01:36:35PM -0400, Scott Murray wrote:
>
> Are you interested in this reservation code as a seperate patch for 2.4,
> or should I just send you all of my cPCI stuff to look at in one go? I
> was going to cut it up into 3-4 patches before sending it to
> pcihpd-discuss sometime later today, but I can do whatever you want.
I'd prefer it for 2.5 right now. But if the cPCI stuff doesn't touch
anything else, I'd be interested in that for 2.4.
I don't want to really touch the core PCI code in 2.4 right now, unless
we _really_ have to :)
> Done. I'd considered doing that right off, but it didn't seem to match
> the style of the rest of the PCI code, for example the proc and pm stuff.
> If you want, I can work on a patch to clean those up as well.
For 2.5, I'd love a patch to do that. As I said above, I don't really
care about that for 2.4.
thanks,
greg k-h
next prev parent reply other threads:[~2002-08-08 18:18 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
2002-08-08 17:36 ` Scott Murray
2002-08-08 18:19 ` Greg KH [this message]
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=20020808181931.GA22209@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.