Hi Bjorn, >-----Original Message----- >From: Bjorn Helgaas [mailto:helg...@kernel.org] >Sent: 24 July 2020 00:23 >To: Shiju Jose <shiju.j...@huawei.com> >Cc: linux-a...@vger.kernel.org; linux-...@vger.kernel.org; linux- >ker...@vger.kernel.org; r...@rjwysocki.net; b...@alien8.de; >james.mo...@arm.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) ><wangkefeng.w...@huawei.com>; jroe...@suse.de; Linuxarm ><linux...@huawei.com>; yangyicong <yangyic...@huawei.com>; Jonathan >Cameron <jonathan.came...@huawei.com>; tanxiaofei ><tanxiao...@huawei.com> >Subject: Re: [PATCH v13 0/2] ACPI / APEI: Add support to notify the vendor >specific HW errors > >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 otherwise allow a driver to recover from an >error. >> The UEFI spec calls these 'Non-standard Section Body' (N.2.3 of >> version 2.8). >> >> patch set >> 1. add a notifier chain for these non-standard/vendor-records >> in the ghes driver. >> >> 2. add a driver to handle HiSilicon HIP PCIe controller's errors. >> >> Changes: >> >> V13: >> 1. Following changes in the HIP PCIe error handling driver. >> 1.1 Add Bjorn's acked-by. >> 1.2. Address the comments and macros order Bjorn mentioned. >> Fix the words in the commit. > >This series is ill-formed: > > - Jul 22 5:39 Shiju Jose [PATCH v13 0/2] ACPI / APEI: Add support to > not > - Jul 22 5:39 Shiju Jose └─>[PATCH v13 1/2] ACPI / APEI: Add a notifier > - Jul 22 5:42 Shiju Jose [PATCH v13 0/2] ACPI / APEI: Add support to > not > - Jul 22 5:42 Shiju Jose └─>[PATCH v13 2/2] PCI: hip: Add handling of > Hi git send-email failed to send out one patch each time in the patch series due to some internal error. > >Patches 1/2 and 2/2 never appear in the same thread. Both should be replies >to 0/2. And should be only *one* v13 0/2, not two :) > >Bjorn
Thanks, Shiju
