linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gengdongjiu@huawei.com (gengdongjiu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/2] acpi: apei: Add SEI notification type support for ARMv8
Date: Wed, 18 Oct 2017 17:17:27 +0800	[thread overview]
Message-ID: <4b51bd4e-2bf7-3aed-f17c-565b49781009@huawei.com> (raw)
In-Reply-To: <20171018090649.e7qgdf2dwmr7yxc3@pd.tnic>


On 2017/10/18 17:06, Borislav Petkov wrote:
> On Wed, Oct 18, 2017 at 01:00:44PM +0800, gengdongjiu wrote:
>> SError is System Error, which is a asynchronous exception in the Internal CPU.
>>
>> In the ARM RAS Extension, there are mainly two type abort for CPU:
>> SEA(Synchronous External Abort)
>> SEI(SError Interrupt)
> And you're not writing it out as "System Error" because ...?

Thanks Borislav, can I write it as asynchronous exception or asynchronous abort?

  reply	other threads:[~2017-10-18  9:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17  8:02 [PATCH v5 1/2] acpi: apei: remove the unused dead-code for SEA/NMI notification type Dongjiu Geng
2017-10-17  8:02 ` [PATCH v5 2/2] acpi: apei: Add SEI notification type support for ARMv8 Dongjiu Geng
2017-10-17 17:06   ` Borislav Petkov
2017-10-18  5:00     ` gengdongjiu
2017-10-18  9:06       ` Borislav Petkov
2017-10-18  9:17         ` gengdongjiu [this message]
2017-10-18  9:25           ` Borislav Petkov
2017-10-18  9:44             ` James Morse
2017-10-18 10:04               ` Borislav Petkov
2017-10-18 10:25                 ` gengdongjiu
2017-10-18 10:21               ` gengdongjiu
2017-10-18 10:26   ` James Morse
2017-10-18 11:39     ` gengdongjiu
2017-10-17 14:06 ` [PATCH v5 1/2] acpi: apei: remove the unused dead-code for SEA/NMI notification type Tyler Baicar
2017-10-17 16:43 ` Borislav Petkov
2017-10-18  3:04   ` gengdongjiu
2017-10-18 10:17     ` Borislav Petkov
2017-10-18 12:27       ` gengdongjiu
2017-10-18 13:14         ` Borislav Petkov

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=4b51bd4e-2bf7-3aed-f17c-565b49781009@huawei.com \
    --to=gengdongjiu@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).