From: Rajesh Shah <rajesh.shah@intel.com>
To: tony.luck-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: FW: [RFC/Patch 0/12] ACPI based root bridge hot-add
Date: Fri, 18 Mar 2005 22:34:10 +0000 [thread overview]
Message-ID: <20050318143410.A1753@unix-os.sc.intel.com> (raw)
I just sent out a series of acpi based root bridge hot-add
patches. I realized that I didn't send the explanation to
all the mailing lists, sorry.
Rajesh
----- Forwarded message from Rajesh Shah <rajesh.shah@intel.com> -----
> Date: Fri, 18 Mar 2005 13:38:57 -0800
> From: Rajesh Shah <rajesh.shah@intel.com>
> To: gregkh@suse.de
> Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
> pcihpd-discuss@lists.sourceforge.net
> Subject: [RFC/Patch 0/12] ACPI based root bridge hot-add
>
> Here is a series of patches to support ACPI hot-add of a root
> bridge hierarchy. The added hierarchy may contain other p2p
> bridges and end/leaf I/O devices too. The root bridge itself is
> assumed to have been assigned resource ranges, but the p2p
> bridges and end devices are not required to be initialized by
> firmware. Most of the code changes are to make the existing code
> flows suitable for such a hierarchy of bridges & devices.
>
> This code supports hot-add on ia64 only for now.It does not yet
> support I/O APIC hot-add, which is needed to make this fully
> functional. The patches are against 2.6.11-mm4 (plus the patch
> needed for ia64 to boot). I've tested to make sure this does not
> break end/leaf device hotplug on the hotplug capable ia64 box I have.
>
> Thanks,
> Rajesh
----- End forwarded message -----
reply other threads:[~2005-03-18 22:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050318143410.A1753@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony.luck-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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