mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: Shuuichirou Ishii <ishii.shuuichir@fujitsu.com>,
	<rafael@kernel.org>, <lenb@kernel.org>,
	<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <lorenzo.pieralisi@arm.com>, <sudeep.holla@arm.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] acpi/tables: Add AEST in ACPI Table Definition
Date: Fri, 19 Nov 2021 16:05:25 +0800	[thread overview]
Message-ID: <a71761c6-5b8a-a4d5-c65a-7d3b3cd0d92f@huawei.com> (raw)
In-Reply-To: <20211105041635.1481738-1-ishii.shuuichir@fujitsu.com>

On 2021/11/5 12:16, Shuuichirou Ishii wrote:
> When We added AEST using the Upgrading ACPI tables via initrd function,
> the kernel could not recognize the AEST, so We added AEST the ACPI table
> definition.

Maybe "so add the AEST table to the list to enable the table upgrade
function." is better?

> 
> Signed-off-by: Shuuichirou Ishii <ishii.shuuichir@fujitsu.com>
> ---
>   drivers/acpi/tables.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/acpi/tables.c b/drivers/acpi/tables.c
> index 71419eb16e09..2699bf7e21ab 100644
> --- a/drivers/acpi/tables.c
> +++ b/drivers/acpi/tables.c
> @@ -500,7 +500,7 @@ static const char table_sigs[][ACPI_NAMESEG_SIZE] __initconst = {
>   	ACPI_SIG_WDDT, ACPI_SIG_WDRT, ACPI_SIG_DSDT, ACPI_SIG_FADT,
>   	ACPI_SIG_PSDT, ACPI_SIG_RSDT, ACPI_SIG_XSDT, ACPI_SIG_SSDT,
>   	ACPI_SIG_IORT, ACPI_SIG_NFIT, ACPI_SIG_HMAT, ACPI_SIG_PPTT,
> -	ACPI_SIG_NHLT };
> +	ACPI_SIG_NHLT, ACPI_SIG_AEST };
>   
>   #define ACPI_HEADER_SIZE sizeof(struct acpi_table_header)

Other than that, I'm fine with this patch.

Acked-by: Hanjun Guo <guohanjun@huawei.com>

Thanks
Hanjun

  parent reply	other threads:[~2021-11-19  8:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  4:16 Shuuichirou Ishii
2021-11-19  7:42 ` ishii.shuuichir
2021-11-19  8:05 ` Hanjun Guo [this message]
2021-11-24  0:52   ` ishii.shuuichir
2021-11-24  7:11     ` Hanjun Guo
2021-11-25  0:32       ` 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=a71761c6-5b8a-a4d5-c65a-7d3b3cd0d92f@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

all inboxes | Powered by JetHome®