mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tyler Baicar <tbaicar@codeaurora.org>
Cc: bp@suse.de, tony.luck@intel.com, will.deacon@arm.com,
	james.morse@arm.com, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 2/2] acpi: apei: call into AER handling regardless of severity
Date: Sat, 18 Nov 2017 15:54:19 +0100	[thread overview]
Message-ID: <9355728.o7rQ576JL4@aspire.rjw.lan> (raw)
In-Reply-To: <1510758867-15940-1-git-send-email-tbaicar@codeaurora.org>

On Wednesday, November 15, 2017 4:14:27 PM CET Tyler Baicar wrote:
> Currently the GHES code only calls into the AER driver for
> recoverable type errors. This is incorrect because errors of
> other severities do not get logged by the AER driver and do not
> get exposed to user space via the AER trace event. So, call
> into the AER driver for PCIe errors regardless of the severity

Can you please resend the [1/2] too for completeness?

Thanks,
Rafael

  reply	other threads:[~2017-11-18 14:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 15:14 Tyler Baicar
2017-11-18 14:54 ` Rafael J. Wysocki [this message]
2017-11-28 10:57 ` Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2017-11-08 19:13 [PATCH 0/2] Restructure and fix GHES PCIe AER handling Tyler Baicar
2017-11-08 19:13 ` [PATCH V3 2/2] acpi: apei: call into AER handling regardless of severity Tyler Baicar
2017-11-09  9:46   ` Borislav Petkov
2017-11-09 14:37     ` Tyler Baicar
2017-11-09 15:01       ` Borislav Petkov
2017-11-09 15:14     ` Tyler Baicar
2017-11-09 17:29       ` Borislav Petkov
2017-11-13 12:36   ` Dongdong Liu
2017-11-13 15:34     ` 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=9355728.o7rQ576JL4@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=bp@suse.de \
    --cc=james.morse@arm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tbaicar@codeaurora.org \
    --cc=tony.luck@intel.com \
    --cc=will.deacon@arm.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
Powered by JetHome