[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58410A5E.8010201@huawei.com>
Date: Fri, 2 Dec 2016 13:45:02 +0800
From: Hanjun Guo <guohanjun@...wei.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Borislav Petkov <bp@...en8.de>
CC: Borislav Petkov <bp@...nel.org>,
Prarit Bhargava <prarit@...hat.com>,
<linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Len Brown <lenb@...nel.org>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Tyler Baicar <tbaicar@...eaurora.org>,
"Punit Agrawal" <punit.agrawal@....com>,
Don Zickus <dzickus@...hat.com>,
Linux ACPI <linux-acpi@...r.kernel.org>
Subject: Re: [PATCH v2] ACPI / APEI: Fix NMI notification handling
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
Powered by blists - more mailing lists