Hi Andy,
>-----Original Message-----
>From: Andy Shevchenko [mailto:andriy.shevche...@linux.intel.com]
>Sent: 22 July 2020 12:02
>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; helg...@kernel.org;
>b...@alien8.de; james.mo...@arm.com; l...@kernel.org;
>tony.l...@intel.com; dan.carpen...@oracle.com;
>zhangligu...@linux.alibaba.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 1/2] ACPI / APEI: Add a notifier chain for unknown
>(vendor) CPER records
>
>On Wed, Jul 22, 2020 at 11:39:51AM +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).
>>
>> Add a notifier chain for these non-standard/vendor-records. Callers
>> must identify their type of records by GUID.
>>
>> Record data is copied to memory from the ghes_estatus_pool to allow us
>> to keep it until after the notifier has run.
>>
>> Co-developed-by: James Morse <james.mo...@arm.com>
>
>Co-developed-by: is going _in conjunction with_ SoB tag which is missing
>here.
This tag was added as per instruction from Rafael.
I was told that I cannot add SoB tag for others unless specifically given.
Probably I will leave it with Rafael/James to help on this SoB tag
as Rafael was ok to merge this patch.
>
>> Signed-off-by: Shiju Jose <shiju.j...@huawei.com>
>
>--
>With Best Regards,
>Andy Shevchenko
>
Thanks,
Shiju
