From: Tyler Baicar <tbaicar@codeaurora.org>
To: rjw@rjwysocki.net, lenb@kernel.org, bhelgaas@google.com,
paul.gortmaker@windriver.com, sudipm.mukherjee@gmail.com,
axboe@fb.com, izumi.taku@jp.fujitsu.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Cc: bp@suse.de, Tyler Baicar <tbaicar@codeaurora.org>
Subject: [PATCH V2 0/2] Correct AER severity for printing AER information
Date: Wed, 14 Sep 2016 15:14:44 -0600 [thread overview]
Message-ID: <1473887686-24420-1-git-send-email-tbaicar@codeaurora.org> (raw)
AER severity handling has two issues that cause the AER information to
be printed incorrectly. The first issue is that the function to calculate
the AER severity is called twice in the code path to print the AER
information. The second issue is that the original call to calculate the
AER severity expects the CPER severity but is recieving the GHES
severity.
V2: Fix minor typo in commit text.
V1: https://lkml.org/lkml/2016/9/12/1075
Tyler Baicar (2):
PCI/AER: Remove duplicate AER severity translation
acpi: apei: send correct severity to calculate AER severity
drivers/acpi/apei/ghes.c | 2 +-
drivers/pci/pcie/aer/aerdrv_errprint.c | 6 ++----
include/linux/aer.h | 2 +-
3 files changed, 4 insertions(+), 6 deletions(-)
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next reply other threads:[~2016-09-14 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 21:14 Tyler Baicar [this message]
2016-09-14 21:14 ` [PATCH V2 1/2] PCI/AER: Remove duplicate AER severity translation Tyler Baicar
2016-09-14 21:14 ` [PATCH V2 2/2] acpi: apei: send correct severity to calculate AER severity Tyler Baicar
2016-09-20 19:41 ` [PATCH V2 0/2] Correct AER severity for printing AER information Bjorn Helgaas
2016-09-21 0:27 ` Rafael J. Wysocki
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=1473887686-24420-1-git-send-email-tbaicar@codeaurora.org \
--to=tbaicar@codeaurora.org \
--cc=axboe@fb.com \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=izumi.taku@jp.fujitsu.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rjw@rjwysocki.net \
--cc=sudipm.mukherjee@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.