From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Mario.Limonciello@dell.com,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH v1 2/2] PCI: shpchp: Fix AMD POGO identification
Date: Sat, 2 Jun 2018 21:49:33 +0300 [thread overview]
Message-ID: <20180602184933.GU15419@lahna.fi.intel.com> (raw)
In-Reply-To: <152791813206.257724.14863139556803168986.stgit@bhelgaas-glaptop.roam.corp.google.com>
On Sat, Jun 02, 2018 at 12:42:12AM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> The fix for an AMD POGO erratum related to SHPC incorrectly identified the
> device. The workaround should be applied only for AMD POGO devices, but it
> was instead applied to:
>
> - all AMD bridges, and
> - all devices from any vendor with device ID 0x7458
Good catch.
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2018-06-02 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 5:41 [PATCH v1 0/2] PCI: shpchp: Minor fixes Bjorn Helgaas
2018-06-02 5:42 ` [PATCH v1 1/2] PCI: shpchp: Use dev_printk() for OSHP-related messages Bjorn Helgaas
2018-06-02 18:48 ` Mika Westerberg
2018-06-03 7:58 ` Rafael J. Wysocki
2018-06-02 5:42 ` [PATCH v1 2/2] PCI: shpchp: Fix AMD POGO identification Bjorn Helgaas
2018-06-02 18:49 ` Mika Westerberg [this message]
2018-06-03 7:59 ` Rafael J. Wysocki
2018-06-04 17:49 ` [PATCH v1 0/2] PCI: shpchp: Minor fixes Bjorn Helgaas
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=20180602184933.GU15419@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Mario.Limonciello@dell.com \
--cc=YehezkelShB@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=rjw@rjwysocki.net \
/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