From: Len Brown <len.brown@intel.com>
To: Greg KH <gregkh@suse.de>
Cc: "Shah, Rajesh" <rajesh.shah@intel.com>,
"linux-pci@atrey.karlin.mff.cuni.cz"
<linux-pci@atrey.karlin.mff.cuni.cz>,
linux-kernel@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>, Tony Luck <tony.luck@intel.com>,
"Sy, Dely L" <dely.l.sy@intel.com>
Subject: Re: [RFC/Patch 0/12] ACPI based root bridge hot-add
Date: 31 Mar 2005 14:06:38 -0500 [thread overview]
Message-ID: <1112295995.2110.38.camel@d845pe> (raw)
In-Reply-To: <20050321182745.GA5201@suse.de>
On Mon, 2005-03-21 at 13:27, Greg KH wrote:
> On Mon, Mar 21, 2005 at 10:04:57AM -0800, Rajesh Shah wrote:
> > > - Are you wanting the acpi specific patches to go into the
> tree
> > > through the acpi developers? How about the ia64 specific
> > > patches?
> >
> > I honestly don't know what the best approach is here - what do you
> > recommend? I did receive an email from Andrew indicating he wants
> > to pick these up for the next mm. Perhaps the best thing is to
> > let Andrew include the whole series after I've addressed all
> > feedback and you, Tony, Len etc. all agree these are OK to go in.
>
> That sounds like a fine plan to me.
Me too.
And I don't see any issues with the ACPI specific changes.
cheers,
-Len
next prev parent reply other threads:[~2005-03-31 19:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 21:38 [RFC/Patch 0/12] ACPI based root bridge hot-add Rajesh Shah
2005-03-18 21:48 ` [Patch 1/12] " Rajesh Shah
2005-03-18 21:59 ` [Patch 2/12] Fix pci_enable_device() for p2p bridges Rajesh Shah
2005-03-18 22:02 ` [patch 03/12] Make pcibios_fixup_bus() hot-plug safe Rajesh Shah
2005-03-18 22:04 ` [patch 04/12] Prevent duplicate bus numbers when scanning PCI bridge Rajesh Shah
2005-03-18 22:07 ` [patch 05/12] Take the PCI lock when modifying pci bus or device lists Rajesh Shah
2005-03-18 22:09 ` [patch 06/12] Link newly created pci child bus to its parent on creation Rajesh Shah
2005-03-18 22:11 ` [patch 07/12] Make the PCI remove routines safe for failed hot-plug Rajesh Shah
2005-03-19 5:14 ` Greg KH
2005-03-18 22:14 ` [patch 08/12] Remove hot-plugged devices that could not be allocated resources Rajesh Shah
2005-03-18 22:16 ` [patch 09/12] Read bridge resources when fixing up the bus Rajesh Shah
2005-03-18 22:18 ` [patch 10/12] Allow ACPI .add and .start operations to be done independently Rajesh Shah
2005-03-18 22:20 ` [patch 11/12] Export the interface to get PCI id for an ACPI handle Rajesh Shah
2005-03-18 22:22 ` [patch 12/12] ACPI based root bridge hot-add Rajesh Shah
2005-03-19 5:13 ` [RFC/Patch 0/12] " Greg KH
2005-03-21 18:04 ` Rajesh Shah
2005-03-21 18:27 ` Greg KH
2005-03-31 19:06 ` Len Brown [this message]
2005-03-19 13:50 ` Paul Ionescu
2005-03-21 19:14 ` [ACPI] " Rajesh Shah
-- strict thread matches above, loose matches on Subject: below --
2005-03-22 1:06 Sy, Dely L
2005-03-23 3:13 Dely Sy
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=1112295995.2110.38.camel@d845pe \
--to=len.brown@intel.com \
--cc=akpm@osdl.org \
--cc=dely.l.sy@intel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rajesh.shah@intel.com \
--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