From: Rajesh Shah <rajesh.shah@intel.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net, akpm@osdl.org,
len.brown@intel.com, tony.luck@intel.com, dely.l.sy@intel.com
Subject: Re: [RFC/Patch 0/12] ACPI based root bridge hot-add
Date: Mon, 21 Mar 2005 10:04:57 -0800 [thread overview]
Message-ID: <20050321100457.A4477@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050319051331.GC21485@suse.de>; from gregkh@suse.de on Fri, Mar 18, 2005 at 09:13:32PM -0800
On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote:
>
> This all looks very good, nice job. I only had one minor comment on the
> patches, which I'll reply to directly.
>
> But I did have a few questions:
> - This series relys on Mathew's rewrite of the acpiphp driver.
> Is that acceptable? Is that patch necessary for your work?
> And if so, can you include it in the whole series?
The last patch (12) in the series is the only one that depends on
Matthew's acpiphp rewrite. I do have a really old version of my
patch that worked with the original acpiphp code base but this
version is cleaner. I could probably resurrect my old patch if you
want, but I'd rather prefer to work on and fix any other objections
you or others may have with Matthew's re-write, since that's the
better overall approach.
> - Does this break the i386 acpiphp functionality?
Dely Sy had tested hotplug with an earlier version of my patches
(with minor differences from the current series) on i386 and it
worked fine. She probably hasn't tested the latest one. Dely,
could you check that please? The i386 hotplug capable box I
have doesn't seem to have the right firmware, so I haven't
been able to test hotplug on that (I'm working on fixing that).
Of course, I tested my patches on i386 (ACPI as well as non-ACPI)
and x86_64 machines to make sure I didn't break boot on those.
> - Have you tested other pci hotplug systems with this patch
> series? Like pci express hotplug, standard pci hotplug,
> cardbus, etc?
No, because I the one system I have access to isn't doing any
hot-plug. I'm working on fixing that but was also hoping to hear
from others who surely have access to more machines than I do.
> - 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.
> - Have the acpi developers agreed with your acpi patches?
>
This is the first time I sent the patches to the acpi list, so I do
need to give them a few days to weigh in.
Rajesh
next prev parent reply other threads:[~2005-03-21 18:05 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 [this message]
2005-03-21 18:27 ` Greg KH
2005-03-31 19:06 ` Len Brown
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=20050321100457.A4477@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=akpm@osdl.org \
--cc=dely.l.sy@intel.com \
--cc=gregkh@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=pcihpd-discuss@lists.sourceforge.net \
--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