From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>,
Robert Richter <rrichter@amd.com>,
Terry Bowman <terry.bowman@amd.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 0/3] PCI/AER: Clean up logging
Date: Fri, 8 Dec 2023 10:54:08 -0600 [thread overview]
Message-ID: <20231208165408.GA796794@bhelgaas> (raw)
In-Reply-To: <20231206224231.732765-1-helgaas@kernel.org>
[+cc Jonathan]
On Wed, Dec 06, 2023 at 04:42:28PM -0600, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> Clean up some minor AER logging issues:
>
> - Log as "Correctable errors", not "Corrected errors"
>
> - Decode the Requester ID when we couldn't find detail error info
>
> Bjorn Helgaas (3):
> PCI/AER: Use 'Correctable' and 'Uncorrectable' spec terms for errors
> PCI/AER: Decode Requester ID when no error info found
> PCI/AER: Use explicit register sizes for struct members
>
> drivers/pci/pcie/aer.c | 19 ++++++++++++-------
> include/linux/aer.h | 8 ++++----
> 2 files changed, 16 insertions(+), 11 deletions(-)
Applied to pci/aer for v6.8. Thanks, Jonathan, for your time in
taking a look.
prev parent reply other threads:[~2023-12-08 16:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 22:42 [PATCH 0/3] PCI/AER: Clean up logging Bjorn Helgaas
2023-12-06 22:42 ` [PATCH 1/3] PCI/AER: Use 'Correctable' and 'Uncorrectable' spec terms for errors Bjorn Helgaas
2023-12-08 14:36 ` Jonathan Cameron
2023-12-12 15:00 ` Terry Bowman
2023-12-12 21:23 ` Bjorn Helgaas
2024-01-02 19:23 ` Kuppuswamy Sathyanarayanan
2023-12-06 22:42 ` [PATCH 2/3] PCI/AER: Decode Requester ID when no error info found Bjorn Helgaas
2023-12-08 14:38 ` Jonathan Cameron
2023-12-12 15:00 ` Terry Bowman
2024-01-02 19:22 ` Kuppuswamy Sathyanarayanan
2024-01-02 22:53 ` Bjorn Helgaas
2023-12-06 22:42 ` [PATCH 3/3] PCI/AER: Use explicit register sizes for struct members Bjorn Helgaas
2023-12-08 14:38 ` Jonathan Cameron
2023-12-08 16:54 ` Bjorn Helgaas [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=20231208165408.GA796794@bhelgaas \
--to=helgaas@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=rrichter@amd.com \
--cc=terry.bowman@amd.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).