[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161201224717.4tkp5glpib5fhusv@pd.tnic>
Date: Thu, 1 Dec 2016 23:47:17 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
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 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 :-)
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists