From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
linux-pci@vger.kernel.org, Matthew Garrett <mjg59@srcf.ucam.org>,
Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Ozan Caglayan <ozan@pardus.org.tr>
Subject: Re: [Resend][PATCH] PCI / ACPI: Request _OSC control once for each root bridge (v3)
Date: Fri, 7 Jan 2011 14:28:32 -0800 [thread overview]
Message-ID: <20110107142832.5f4f1ae5@jbarnes-desktop> (raw)
In-Reply-To: <201101070055.10065.rjw@sisk.pl>
On Fri, 7 Jan 2011 00:55:09 +0100
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> Move the evaluation of acpi_pci_osc_control_set() (to request control
> of PCI Express native features) into acpi_pci_root_add() to avoid
> calling it many times for the same root complex with the same
> arguments. Additionally, check if all of the requisite _OSC
> support bits are set before calling acpi_pci_osc_control_set() for
> a given root complex.
>
> References: https://bugzilla.kernel.org/show_bug.cgi?id=20232
> Reported-by: Ozan Caglayan <ozan@pardus.org.tr>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
>
> Hi,
>
> This fixes a post-2.6.35 regression for Ozan, possibly -stable material.
>
Applied, thanks, but I forgot the cc: stable, so please send the commit
id to stable@ once it lands in Linus's tree, if you still think it's
appropriate.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2011-01-07 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 23:55 [Resend][PATCH] PCI / ACPI: Request _OSC control once for each root bridge (v3) Rafael J. Wysocki
2011-01-07 6:14 ` Ozan Çağlayan
2011-01-07 22:28 ` 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=20110107142832.5f4f1ae5@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=ozan@pardus.org.tr \
--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