From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Alex Chiang <achiang@hp.com>
Cc: kristen.c.accardi@intel.com, garyhade@us.ibm.com,
linux-pci@vger.kernel-org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI Hotplug: acpiphp: cleanup notify handler on all root bridges
Date: Wed, 2 Jul 2008 11:41:23 -0700 [thread overview]
Message-ID: <200807021141.24600.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080702020223.GA32046@ldl.fc.hp.com>
On Tuesday, July 01, 2008 7:02 pm Alex Chiang wrote:
> Hi Jesse, Kristen,
>
> During the development of the physical PCI slot patch series,
> Gary Hade kept on reporting strange oopses due to interactions
> between pci_slot and acpiphp.
>
> http://lkml.org/lkml/2007/11/28/319
>
> He got busy and went away for a while, and that's when I was able
> to sneak my patchset into Jesse's linux-next branch. ;)
>
> Recently, Gary got some time to test again on his x3950 M2
> system, and together, we finally figured out the oops.
>
> This bug has always been present in acpiphp so it's not a
> regression. So if you want to hold off until the next merge
> window, I'm ok with that.
>
> Otherwise, I feel it's pretty low-risk and could go into the next
> -rc. Totally your call, I have no strong feelings either way.
given that it fixes some pretty bad behavior, I went ahead and pushed this
into my pull request for Linus. Thanks for cleaning it up, the hotplug code
is looking much better these days thanks to yours and Kenji-san's efforts.
Jesse
prev parent reply other threads:[~2008-07-02 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 2:02 [PATCH] PCI Hotplug: acpiphp: cleanup notify handler on all root bridges Alex Chiang
2008-07-02 18:41 ` Jesse Barnes [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=200807021141.24600.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=achiang@hp.com \
--cc=garyhade@us.ibm.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel-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