From: Dan Carpenter <dan.carpenter@oracle.com>
To: Shiju Jose <shiju.jose@huawei.com>, James Morse <james.morse@arm.com>
Cc: linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, rjw@rjwysocki.net,
helgaas@kernel.org, bp@alien8.de, lenb@kernel.org,
tony.luck@intel.com, zhangliguang@linux.alibaba.com,
andriy.shevchenko@linux.intel.com, wangkefeng.wang@huawei.com,
jroedel@suse.de, linuxarm@huawei.com, yangyicong@hisilicon.com,
jonathan.cameron@huawei.com, tanxiaofei@huawei.com
Subject: Re: [PATCH v11 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors
Date: Mon, 22 Jun 2020 15:45:43 +0300 [thread overview]
Message-ID: <20200622124543.GV4282@kadam> (raw)
In-Reply-To: <20200622120527.690-1-shiju.jose@huawei.com>
On Mon, Jun 22, 2020 at 01:05:25PM +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:
>
> V11:
> 1. Following modifications made by James Morse in the APEI patch
> for the vendor error record.
> - Removed kfifo and ghes_gdata_pool. Expanded commit message.
>
> Note: Kept the Signed-off-by: James Morse as he is given
> because I am not sure the right format.
Wait, what? He doesn't seem to have given any S-o-b in the public
thread.
Signed-off-by means that you handled a patch. Presumably you are the
maintainer and hopefully you looked at the patch before applying it.
Signed-off-by is like signing a legal document to say that you didn't
add any Top Secrety SCO UNIXWare source code. Reviewed-by means you
reviewed it and approve. Acked-by means you approve the patch which
sort of means you are the maintainer or you care about it for some
reason, for example, maybe there was a debate and you like the chosen
approach.
regards,
dan carpenter
prev parent reply other threads:[~2020-06-22 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 12:05 [PATCH v11 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Shiju Jose
2020-06-22 12:05 ` [PATCH v11 1/2] ACPI / APEI: Add a notifier chain for unknown (vendor) CPER records Shiju Jose
2020-07-13 8:35 ` Shiju Jose
2020-07-13 11:17 ` Rafael J. Wysocki
2020-07-13 13:33 ` Shiju Jose
2020-07-13 13:38 ` Rafael J. Wysocki
2020-07-13 13:50 ` Shiju Jose
2020-06-22 12:45 ` Dan Carpenter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200622124543.GV4282@kadam \
--to=dan.carpenter@oracle.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=helgaas@kernel.org \
--cc=james.morse@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=jroedel@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rjw@rjwysocki.net \
--cc=shiju.jose@huawei.com \
--cc=tanxiaofei@huawei.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yangyicong@hisilicon.com \
--cc=zhangliguang@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).