From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/ACPI: Report ASPM support to BIOS if not disabled from command line
Date: Fri, 18 Mar 2011 10:52:52 -0700 [thread overview]
Message-ID: <20110318105252.1d896bb6@jbarnes-desktop> (raw)
In-Reply-To: <201103181841.28636.rjw@sisk.pl>
On Fri, 18 Mar 2011 18:41:28 +0100
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> On Friday, March 18, 2011, Jesse Barnes wrote:
> > On Fri, 18 Mar 2011 01:25:56 +0000
> > Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> >
> > > On Fri, Mar 18, 2011 at 10:10:20AM +0900, Kenji Kaneshige wrote:
> > > > Jesse,
> > > >
> > > > This patch fixes the problem that PCIe hotplug no longer work in
> > > > 2.6.38 on my platform (ASPM is disabled through ACPI FADT in my
> > > > platform). I think this need to be applied soon.
> > > >
> > > > Reviewed-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
> > > > Tested-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
> > >
> > > Yes, I think we need to look at -stable for this one.
> >
> > Ok, thanks guys. I'll queue it up in -fixes and send it to Linus after
> > my 2.6.39 pull req with a cc for stable.
>
> Well, I thought you could simply include it into the pull request. :-)
I could have if I had applied it last week...
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-03-18 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 12:21 [PATCH] PCI/ACPI: Report ASPM support to BIOS if not disabled from command line Rafael J. Wysocki
2011-03-18 1:10 ` Kenji Kaneshige
2011-03-18 1:25 ` Matthew Garrett
2011-03-18 4:41 ` Jesse Barnes
2011-03-18 17:41 ` Rafael J. Wysocki
2011-03-18 17:52 ` Jesse Barnes [this message]
2011-03-21 16:37 ` Jesse Barnes
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=20110318105252.1d896bb6@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
/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