From: Borislav Petkov <bp@suse.de>
To: Tyler Baicar <tbaicar@codeaurora.org>
Cc: rjw@rjwysocki.net, lenb@kernel.org, bhelgaas@google.com,
matt.fleming@intel.com, paul.gortmaker@windriver.com,
zjzhang@codeaurora.org, 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
Subject: Re: [PATCH 0/2] Correct AER severity for printing AER information
Date: Tue, 13 Sep 2016 10:45:31 +0200 [thread overview]
Message-ID: <20160913084531.GA19076@nazgul.tnic> (raw)
In-Reply-To: <1473713845-23613-1-git-send-email-tbaicar@codeaurora.org>
On Mon, Sep 12, 2016 at 02:57:23PM -0600, Tyler Baicar wrote:
> 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.
>
> 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(-)
For both:
Reviewed-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2016-09-13 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 20:57 Tyler Baicar
2016-09-12 20:57 ` [PATCH 1/2] PCI/AER: Remove duplicate AER severity translation Tyler Baicar
2016-09-12 20:57 ` [PATCH 2/2] acpi: apei: send correct severity to calculate AER severity Tyler Baicar
2016-09-13 8:45 ` Borislav Petkov [this message]
2016-09-14 21:12 [PATCH 0/2] Correct AER severity for printing AER information Tyler Baicar
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=20160913084531.GA19076@nazgul.tnic \
--to=bp@suse.de \
--cc=axboe@fb.com \
--cc=bhelgaas@google.com \
--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=matt.fleming@intel.com \
--cc=paul.gortmaker@windriver.com \
--cc=rjw@rjwysocki.net \
--cc=sudipm.mukherjee@gmail.com \
--cc=tbaicar@codeaurora.org \
--cc=zjzhang@codeaurora.org \
/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
all inboxes | Powered by JetHome®