From: Kristen Accardi <kristen.c.accardi@intel.com>
To: pcihpd-discuss@lists.sourceforge.net,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Cc: rajesh.shah@intel.com, greg@kroah.com, len.brown@intel.com
Subject: [patch 0/2] acpiphp: hotplug adapters with bridges on them
Date: Fri, 07 Oct 2005 10:45:45 -0700 [thread overview]
Message-ID: <1128707145.11020.9.camel@whizzy> (raw)
These 2 patches will allow adapters with p2p bridges on them to be
successfully hotplugged using the acpiphp driver. Currently, if you
attempt to hotplug an adapter with a p2p bridge on it, the operation
will fail because resources are not allocated to it properly. These
patches have had very limited testing as I only have one machine and one
type of adapter to test this with. I tested this with 2.6.14-rc2, but
the patch applies fine to rc3 as well.
next reply other threads:[~2005-10-07 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 17:45 Kristen Accardi [this message]
2005-10-13 11:29 ` [patch 0/2] acpiphp: hotplug adapters with bridges on them Paul Ionescu
2005-10-17 17:41 ` [ACPI] " Kristen Accardi
2005-10-17 19:09 ` Paul Ionescu
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=1128707145.11020.9.camel@whizzy \
--to=kristen.c.accardi@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rajesh.shah@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