On Fri, Jul 24, 2020 at 09:08:16AM +, Shiju Jose wrote:
> >-Original Message-
> >From: Bjorn Helgaas [mailto:helg...@kernel.org]
> >Sent: 24 July 2020 00:23
> >On Wed, Jul 22, 2020 at 11:42:43AM +0100, Shiju Jose wrote:
...
> >This series is ill-formed:
I confirm this.
> > - Jul 22
.com; l...@kernel.org; tony.l...@intel.com;
>dan.carpen...@oracle.com; zhangligu...@linux.alibaba.com;
>andriy.shevche...@linux.intel.com; Wangkefeng (OS Kernel Lab)
>; jroe...@suse.de; Linuxarm
>; yangyicong ; Jonathan
>Cameron ; tanxiaofei
>
>Subject: Re: [PATCH v13 0/2] ACP
On Wed, Jul 22, 2020 at 11:42:43AM +0100, Shiju Jose wrote:
> CPER records describing a firmware-first error are identified by GUID.
> The ghes driver currently logs, but ignores any unknown CPER records.
> This prevents describing errors that can't be represented by a standard
> entry, that would
CPER records describing a firmware-first error are identified by GUID.
The ghes driver currently logs, but ignores any unknown CPER records.
This prevents describing errors that can't be represented by a standard
entry, that would otherwise allow a driver to recover from an error.
The UEFI spec cal
CPER records describing a firmware-first error are identified by GUID.
The ghes driver currently logs, but ignores any unknown CPER records.
This prevents describing errors that can't be represented by a standard
entry, that would otherwise allow a driver to recover from an error.
The UEFI spec cal
5 matches
Mail list logo
