From: Greg KH <greg@kroah.com>
To: Scott Murray <scottm@somanetworks.com>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
"Lee, Jung-Ik" <jung-ik.lee@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: bare pci configuration access functions ?
Date: Thu, 31 Oct 2002 15:46:21 -0800 [thread overview]
Message-ID: <20021031234621.GE10689@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0210311748050.26260-100000@rancor.yyz.somanetworks.com>
On Thu, Oct 31, 2002 at 05:50:06PM -0500, Scott Murray wrote:
> On Thu, 31 Oct 2002, Greg KH wrote:
> [snip]
> > Anyway, this is a nice diversion from the real problem here, for 2.4,
> > should I just backport the pci_ops changes which will allow pci
> > hotplugging to work again on ia64, or do we want to do something else?
>
> It would be nice from a hotplug driver maintenance point of view if the
> 2.4 and 2.5 interfaces were the same IMO.
Yes it would be, but it's not a necessary thing :)
> How about submitting the change in 2.4.21-pre?
It is a _very_ big change. It hits every architecture. It was the
right thing to do in 2.5, I'm just questioning if it's the right thing
to do in 2.4 because of the magnitude of it.
So, if people say it's ok, I'll do it. But I would like to hear from
the PPC64 group first, as I know I caused them a lot of grief and rework
because of it.
thanks,
greg k-h
next prev parent reply other threads:[~2002-10-31 23:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 22:00 bare pci configuration access functions ? Grover, Andrew
2002-10-31 22:11 ` Greg KH
2002-10-31 22:50 ` Scott Murray
2002-10-31 23:46 ` Greg KH [this message]
2002-11-01 0:23 ` Scott Murray
2002-10-31 23:37 ` KOCHI, Takayoshi
2002-10-31 23:54 ` Greg KH
2002-11-01 0:23 ` KOCHI, Takayoshi
2002-11-01 1:13 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-11-01 2:07 Grover, Andrew
2002-11-01 2:45 ` Greg KH
2002-10-31 21:07 Grover, Andrew
2002-10-31 21:23 ` Greg KH
2002-10-31 23:40 ` Kai Germaschewski
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=20021031234621.GE10689@kroah.com \
--to=greg@kroah.com \
--cc=andrew.grover@intel.com \
--cc=jung-ik.lee@intel.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.