linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gengdongjiu <gengdongjiu@huawei.com>
To: Will Deacon <will.deacon@arm.com>, gengdongjiu <gengdj.1984@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>, <mark.rutland@arm.com>,
	"Len Brown" <lenb@kernel.org>, <rafael.j.wysocki@intel.com>,
	<erik.schmauss@intel.com>, <robert.moore@intel.com>,
	arm-mail-list <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<linux-acpi@vger.kernel.org>, <devel@acpica.org>
Subject: Re: [PATCH] arm64: clean the additional checks before calling ghes_notify_sea()
Date: Tue, 7 Aug 2018 14:37:36 +0800	[thread overview]
Message-ID: <2c3baa9e-c647-01a9-cef6-eb61ba6c529c@huawei.com> (raw)
In-Reply-To: <20180806142623.GA15275@arm.com>



On 2018/8/6 22:26, Will Deacon wrote:
>> Will,
>>      This patch will be applied, right? thanks
> I haven't queued it in the arm64 tree, since it touches include/acpi/ghes.h
> and you don't have an ack from the acpi folks. I acked it so that you could
> route it via the acpi tree without me holding you up.

Thanks the explanation.
yes, this patch touches the "include/acpi/ghes.h", I will repost this patch to let acpi
folks review it.


> 
> Will
> 
>>>> This cleanup is ever mentioned by Mark Rutland in [1]


  reply	other threads:[~2018-08-07  6:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 21:01 [PATCH] arm64: clean the additional checks before calling ghes_notify_sea() Dongjiu Geng
2018-07-27 10:06 ` Will Deacon
2018-08-05  2:35   ` gengdongjiu
2018-08-06 14:26     ` Will Deacon
2018-08-07  6:37       ` gengdongjiu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-26 21:01 Dongjiu Geng

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=2c3baa9e-c647-01a9-cef6-eb61ba6c529c@huawei.com \
    --to=gengdongjiu@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=devel@acpica.org \
    --cc=erik.schmauss@intel.com \
    --cc=gengdj.1984@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@intel.com \
    --cc=will.deacon@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).