From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Borislav Petkov <bp@kernel.org>
Cc: Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
"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: Thu, 01 Dec 2016 23:29:45 +0100 [thread overview]
Message-ID: <10086382.uM7IovncFW@aspire.rjw.lan> (raw)
In-Reply-To: <20161201215149.fvb3ki77det7bnjq@pd.tnic>
On Thursday, December 01, 2016 10:51:49 PM Borislav Petkov wrote:
> On Thu, Dec 01, 2016 at 10:17:54PM +0100, Rafael J. Wysocki wrote:
> > I guess I should pick up this one, then?
>
> If you already have stuff touching this area, it probably would be more
> prudent if you took it. If not, I can take it through tip's ras branch,
> if you prefer.
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. :-)
Thanks,
Rafael
next prev parent reply other threads:[~2016-12-01 22:34 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 [this message]
2016-12-01 22:47 ` Borislav Petkov
2016-12-01 23:12 ` Rafael J. Wysocki
2016-12-02 5:45 ` Hanjun Guo
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=10086382.uM7IovncFW@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=bp@kernel.org \
--cc=bp@suse.de \
--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=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