From: bp@suse.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/1] acpi: apei: Enable APEI multiple GHES source to share an single external IRQ
Date: Fri, 21 Jul 2017 08:00:07 +0200 [thread overview]
Message-ID: <20170721060007.GA26714@nazgul.tnic> (raw)
In-Reply-To: <1500586563-7088-2-git-send-email-lho@apm.com>
On Thu, Jul 20, 2017 at 02:36:03PM -0700, Loc Ho wrote:
> This patch allows APEI generic error source table with external
"This patch" in a commit message is tautologically redundant.
> IRQ to share a single IRQ.
Because? More background please.
> Co-authored-by: Tuan Phan <tphan@apm.com>
I guess an invented tag is fine. What you can also do is say in free
text in the commit message that Tuan has helped.
> Signed-off-by: Loc Ho <lho@apm.com>
> ---
...
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg)
--
prev parent reply other threads:[~2017-07-21 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 21:36 [PATCH v5 0/1] acpi: apei: Bug fix to enable APEI support for ARMv8 Loc Ho
2017-07-20 21:36 ` [PATCH v5 1/1] acpi: apei: Enable APEI multiple GHES source to share an single external IRQ Loc Ho
2017-07-21 6:00 ` Borislav Petkov [this message]
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=20170721060007.GA26714@nazgul.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