From: Hanjun Guo <guohanjun@huawei.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Borislav Petkov <bp@alien8.de>
Cc: Borislav Petkov <bp@kernel.org>,
Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Tyler Baicar <tbaicar@codeaurora.org>,
Punit Agrawal <punit.agrawal@arm.com>,
Don Zickus <dzickus@redhat.com>,
Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v2] ACPI / APEI: Fix NMI notification handling
Date: Fri, 2 Dec 2016 13:45:02 +0800 [thread overview]
Message-ID: <58410A5E.8010201@huawei.com> (raw)
In-Reply-To: <5033158.rooYzydQzm@aspire.rjw.lan>
On 2016/12/2 7:12, Rafael J. Wysocki wrote:
> On Thursday, December 01, 2016 11:47:17 PM Borislav Petkov wrote:
>> On Thu, Dec 01, 2016 at 11:29:45PM +0100, Rafael J. Wysocki wrote:
>>> Well, there's another ARM-related patch touching APEI.
>>>
>>> I guess whoever takes this one should also take the other one and
>>> honestly they can go in via any tree as far as I'm concerned, I'm just trying to
>>> avoid merge clashes here. :-)
>> Maybe have ARM-folk ACK the other one and take both through your ACPI
>> tree? They both do have ACPI in common :-)
> That one have been ACKed already.
>
> OK, I'll take them both.
Thank you very much :)
Hanjun
next prev parent reply other threads:[~2016-12-02 5:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 18:43 [PATCH] ACPI / APEI: Fix NMI notification handling Prarit Bhargava
2016-11-29 19:36 ` Borislav Petkov
[not found] ` <1480511979-11722-1-git-send-email-prarit@redhat.com>
[not found] ` <20161201200739.qcibekpe37podnmu@pd.tnic>
2016-12-01 21:17 ` [PATCH v2] " Rafael J. Wysocki
[not found] ` <20161201215149.fvb3ki77det7bnjq@pd.tnic>
2016-12-01 22:29 ` Rafael J. Wysocki
2016-12-01 22:47 ` Borislav Petkov
2016-12-01 23:12 ` Rafael J. Wysocki
2016-12-02 5:45 ` Hanjun Guo [this message]
2016-12-02 11:39 ` Fu Wei
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=58410A5E.8010201@huawei.com \
--to=guohanjun@huawei.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=dzickus@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=prarit@redhat.com \
--cc=punit.agrawal@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=tbaicar@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