On Thu, Sep 03, 2020 at 01:34:54PM +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
On Tue, Sep 15, 2020 at 8:17 PM Bjorn Helgaas wrote:
>
> On Tue, Sep 15, 2020 at 07:31:50PM +0200, Rafael J. Wysocki wrote:
> > On Mon, Sep 14, 2020 at 2:34 PM Shiju Jose wrote:
> > >
> > > Hello,
> > >
> > > Can you help to merge this series?
> >
> > Do you want this series to go in through the
kernel.org; tony.l...@intel.com;
> >dan.carpen...@oracle.com; andriy.shevche...@linux.intel.com
> >Cc: Linuxarm
> >Subject: [PATCH v15 0/2] ACPI / APEI: Add support to notify the vendor
> >specific HW errors
> >
> >CPER records describing a firmware-first error
On Tue, Sep 15, 2020 at 07:31:50PM +0200, Rafael J. Wysocki wrote:
> On Mon, Sep 14, 2020 at 2:34 PM Shiju Jose wrote:
> >
> > Hello,
> >
> > Can you help to merge this series?
>
> Do you want this series to go in through the ACPI tree?
It crosses ACPI and vendor-specific PCI, but the bulk of th
vger.kernel.org; r...@rjwysocki.net; helg...@kernel.org;
>b...@alien8.de; james.mo...@arm.com; lorenzo.pieral...@arm.com;
>r...@kernel.org; l...@kernel.org; tony.l...@intel.com;
>dan.carpen...@oracle.com; andriy.shevche...@linux.intel.com
>Cc: Linuxarm
>Subject: [PATCH v15 0/2] ACPI / APEI:
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
6 matches
Mail list logo
