From: gengdongjiu <gengdongjiu@huawei.com>
To: Stephen Boyd <sboyd@codeaurora.org>,
Tyler Baicar <tbaicar@codeaurora.org>
Cc: <will.deacon@arm.com>, <zjzhang@codeaurora.org>,
<catalin.marinas@arm.com>, <bp@suse.de>, <james.morse@arm.com>,
<geliangtang@gmail.com>, <andriy.shevchenko@linux.intel.com>,
<tony.luck@intel.com>, <austinwc@codeaurora.org>,
<rjw@rjwysocki.net>, <lenb@kernel.org>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <john.garry@huawei.com>,
<shiju.jose@huawei.com>, <zhengqiang10@huawei.com>,
<wangxiongfeng2@huawei.com>, <huangshaoyu@huawei.com>,
<wuquanming@huawei.com>
Subject: Re: [PATCH v2] acpi: apei: Add SEI notification type support for ARMv8
Date: Thu, 28 Sep 2017 20:29:13 +0800 [thread overview]
Message-ID: <e33b84a1-def7-7098-cbcf-627de0a24295@huawei.com> (raw)
In-Reply-To: <20170927155210.GF457@codeaurora.org>
Hi Stephen, Tyler
On 2017/9/27 23:52, Stephen Boyd wrote:
>>>> Something to be aware of, this patch will conflict with https://lkml.org/lkml/2017/9/14/663
>>>> It may make sense to just remove the conditions for the NMI configs as part of this patch or in a series with this patch to avoid merge conflicts.
>>> In your patch, you only remove ACPI_APEI_SEA for the ARCH_HAVE_NMI_SAFE_CMPXCHG, do you need to remove it for the HAVE_NMI?
>> From the latest comments it sounds like Stephen was going to remove
>> it from both.
>> https://lkml.org/lkml/2017/9/15/350
> Sent it now.
I updated my patches. hope you can review again. only a little change. thanks
[PATCH v3 1/2] acpi: apei: remove the unused dead-code for SEA notification type
[PATCH v3 2/2] acpi: apei: Add SEI notification type support for ARMv8
prev parent reply other threads:[~2017-09-28 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 7:22 Dongjiu Geng
2017-09-26 19:23 ` Tyler Baicar
2017-09-27 1:30 ` gengdongjiu
2017-09-27 12:05 ` gengdongjiu
2017-09-27 14:19 ` Tyler Baicar
2017-09-27 15:52 ` Stephen Boyd
2017-09-28 12:29 ` gengdongjiu [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=e33b84a1-def7-7098-cbcf-627de0a24295@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=austinwc@codeaurora.org \
--cc=bp@suse.de \
--cc=catalin.marinas@arm.com \
--cc=geliangtang@gmail.com \
--cc=huangshaoyu@huawei.com \
--cc=james.morse@arm.com \
--cc=john.garry@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=shiju.jose@huawei.com \
--cc=tbaicar@codeaurora.org \
--cc=tony.luck@intel.com \
--cc=wangxiongfeng2@huawei.com \
--cc=will.deacon@arm.com \
--cc=wuquanming@huawei.com \
--cc=zhengqiang10@huawei.com \
--cc=zjzhang@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
all inboxes | Powered by JetHome®