From: Alex Chiang <achiang@hp.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-pci@vger.kernel.org, jbarnes@virtuousgeek.org,
djwong@us.ibm.com, Trent Piepho <xyzzy@speakeasy.org>,
linux-kernel@vger.kernel.org
Subject: Re: Q: state of pci express hotplug
Date: Mon, 2 Feb 2009 10:01:07 -0700 [thread overview]
Message-ID: <20090202170107.GA1027@ldl.fc.hp.com> (raw)
In-Reply-To: <m1fxj06js8.fsf@fess.ebiederm.org>
* Eric W. Biederman <ebiederm@xmission.com>:
>
> Trying to use the current pciehp code, on real hardware in an
> interesting topology (more later) I'm not finding it very
> satisfactory at all. I am up to at least three show stopper
> bugs and the code is not doing what I really need it to do, so
> I am looking at a significant rewrite patch effort to make this
> code usable.
Can you send us some bug reports instead of making us just guess?
> Am I unique in thinking there is a lot that needs to be done?
> Is there current work in progress to make the pci hotplug work
> better?
I think we all want to help, but that's hard if we don't know
what's broken on your machine.
Thanks.
/ac
prev parent reply other threads:[~2009-02-02 17:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 7:01 Q: state of pci express hotplug Eric W. Biederman
2009-01-31 18:13 ` Rafael J. Wysocki
2009-02-02 2:19 ` Kenji Kaneshige
2009-02-02 17:15 ` Krishna Kothapalli
2009-02-03 0:51 ` Kenji Kaneshige
2009-02-03 20:48 ` Krishna Kothapalli
2009-02-04 2:32 ` Krishna Kothapalli
2009-02-04 5:51 ` Kenji Kaneshige
2009-02-04 18:17 ` Krishna Kothapalli
2009-02-04 19:40 ` Mark Lord
2009-02-04 23:49 ` Alex Chiang
2009-02-05 0:02 ` Kenji Kaneshige
2009-02-05 1:53 ` Krishna Kothapalli
2009-02-05 6:42 ` Kenji Kaneshige
2009-02-06 20:37 ` Krishna Kothapalli
2009-02-02 17:01 ` Alex Chiang [this message]
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=20090202170107.GA1027@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=djwong@us.ibm.com \
--cc=ebiederm@xmission.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=xyzzy@speakeasy.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