On Fri, Feb 09, 2018 at 02:29:27PM +, David Woodhouse wrote:
On Fri, 2018-02-09 at 14:10 +, Darren Kenny wrote:
According to the latest microcode update from Intel (on Feb 8, 2018) on
Skylake we should be using the microcode revisions 0xC2***, so we need
to remove that from the
On Fri, Feb 09, 2018 at 02:29:27PM +, David Woodhouse wrote:
On Fri, 2018-02-09 at 14:10 +, Darren Kenny wrote:
According to the latest microcode update from Intel (on Feb 8, 2018) on
Skylake we should be using the microcode revisions 0xC2***, so we need
to remove that from the
On Fri, 2018-02-09 at 14:10 +, Darren Kenny wrote:
> According to the latest microcode update from Intel (on Feb 8, 2018) on
> Skylake we should be using the microcode revisions 0xC2***, so we need
> to remove that from the blacklist now.
The doc also suggests that Gemini Lake 0x22 is also
On Fri, 2018-02-09 at 14:10 +, Darren Kenny wrote:
> According to the latest microcode update from Intel (on Feb 8, 2018) on
> Skylake we should be using the microcode revisions 0xC2***, so we need
> to remove that from the blacklist now.
The doc also suggests that Gemini Lake 0x22 is also
According to the latest microcode update from Intel (on Feb 8, 2018) on
Skylake we should be using the microcode revisions 0xC2***, so we need
to remove that from the blacklist now.
Signed-off-by: Darren Kenny
Reviewed-by: Konrad Rzeszutek Wilk
According to the latest microcode update from Intel (on Feb 8, 2018) on
Skylake we should be using the microcode revisions 0xC2***, so we need
to remove that from the blacklist now.
Signed-off-by: Darren Kenny
Reviewed-by: Konrad Rzeszutek Wilk
Tested-by: Konrad Rzeszutek Wilk
---
6 matches
Mail list logo