On Sat, Jun 2, 2018 at 7:42 AM, 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
On Sat, Jun 2, 2018 at 7:42 AM, 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
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,
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,
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
Fixes: 53044f357448
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
Fixes: 53044f357448
6 matches
Mail list logo