From: bp@suse.de (Borislav Petkov)
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 12:04:57 +0200 [thread overview]
Message-ID: <20171018100456.4xthv2tfvgckzyk3@pd.tnic> (raw)
In-Reply-To: <59E72290.6060604@arm.com>
On Wed, Oct 18, 2017 at 10:44:48AM +0100, James Morse wrote:
> What should we call this thing?
My only pet peeve is having abbreviations everywhere and nothing
explaining them.
So whatever you guys decide upon and as long as there's an explanation
what those things mean and you stick with that name, is perfectly fine
with me.
Thx.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg)
--
next prev parent reply other threads:[~2017-10-18 10:04 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
2017-10-18 9:25 ` Borislav Petkov
2017-10-18 9:44 ` James Morse
2017-10-18 10:04 ` Borislav Petkov [this message]
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=20171018100456.4xthv2tfvgckzyk3@pd.tnic \
--to=bp@suse.de \
--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).