From: Bjorn Helgaas <helgaas@kernel.org>
To: Shiju Jose <shiju.jose@huawei.com>
Cc: linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, rjw@rjwysocki.net, bp@alien8.de,
james.morse@arm.com, lenb@kernel.org, tony.luck@intel.com,
dan.carpenter@oracle.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 v13 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors
Date: Thu, 23 Jul 2020 18:23:01 -0500 [thread overview]
Message-ID: <20200723232301.GA1468407@bjorn-Precision-5520> (raw)
In-Reply-To: <20200722104245.1060-1-shiju.jose@huawei.com>
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
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
next prev parent reply other threads:[~2020-07-23 23:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 10:42 [PATCH v13 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Shiju Jose
2020-07-22 10:42 ` [PATCH v13 2/2] PCI: hip: Add handling of HiSilicon HIP PCIe controller errors Shiju Jose
2020-07-23 12:43 ` Shiju Jose
2020-07-23 23:23 ` Bjorn Helgaas [this message]
2020-07-24 9:08 ` [PATCH v13 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Shiju Jose
2020-07-24 12:17 ` andriy.shevchenko
-- strict thread matches above, loose matches on Subject: below --
2020-07-22 10:39 Shiju Jose
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=20200723232301.GA1468407@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=dan.carpenter@oracle.com \
--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).