From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: [PATCH v1 2/2] PCI: shpchp: Fix AMD POGO identification Date: Sat, 2 Jun 2018 21:49:33 +0300 Message-ID: <20180602184933.GU15419@lahna.fi.intel.com> References: <152791788214.257724.13044360353832574147.stgit@bhelgaas-glaptop.roam.corp.google.com> <152791813206.257724.14863139556803168986.stgit@bhelgaas-glaptop.roam.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <152791813206.257724.14863139556803168986.stgit@bhelgaas-glaptop.roam.corp.google.com> Sender: linux-kernel-owner@vger.kernel.org To: Bjorn Helgaas Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, "Rafael J . Wysocki" , Len Brown , Mario.Limonciello@dell.com, Michael Jamet , Yehezkel Bernat , Andy Shevchenko , Lukas Wunner List-Id: linux-acpi@vger.kernel.org On Sat, Jun 02, 2018 at 12:42:12AM -0500, Bjorn Helgaas wrote: > From: Bjorn Helgaas > > 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