From: Hanjun Guo <guohanjun@huawei.com>
To: "ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] acpi/tables: Add AEST in ACPI Table Definition
Date: Mon, 29 Nov 2021 09:01:27 +0800 [thread overview]
Message-ID: <25725e77-d6ba-aa33-6a1e-075f57e1b309@huawei.com> (raw)
In-Reply-To: <TYCPR01MB6160526A9B559655FAEE2DEFE9659@TYCPR01MB6160.jpnprd01.prod.outlook.com>
On 2021/11/29 7:54, ishii.shuuichir@fujitsu.com wrote:
> Hi, Hanjun.
>
> Thank you for your comment.
> We apologize for the basic mistake.
>
> We will try to fix it as follows, is it OK?
>
> ---
> Subject: [PATCH v3] acpi/tables: Add AEST in ACPI Table Definition
>
> When We added AEST using the Upgrading ACPI tables via initrd function,
> the kernel could not recognize the AEST, so added the AEST table to
> the list to enable the table upgrade function.
>
> Signed-off-by: Shuuichirou Ishii <ishii.shuuichir@fujitsu.com>
> ---
> v3 : Changed the location of the change log so that it does not
> disappear when the patch is applied.
>
> v2 : The reason for committing in the commit log was not clear,
> so it was pointed out and corrected.
Looks good to me.
Thanks
Hanjun
next prev parent reply other threads:[~2021-11-29 1:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 8:32 [PATCH v2] acpi/tables: Add AEST in ACPI Table Definition Shuuichirou Ishii
2021-11-27 3:01 ` Hanjun Guo
2021-11-28 23:54 ` ishii.shuuichir
2021-11-29 1:01 ` Hanjun Guo [this message]
2021-11-29 1:33 ` ishii.shuuichir
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=25725e77-d6ba-aa33-6a1e-075f57e1b309@huawei.com \
--to=guohanjun@huawei.com \
--cc=ishii.shuuichir@fujitsu.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=lorenzo.pieralisi@arm.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@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).