From: Hanjun Guo <guohanjun@huawei.com>
To: Stephen Boyd <swboyd@chromium.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: <linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>,
<linux-arm-kernel@lists.infradead.org>,
dann frazier <dann.frazier@canonical.com>,
Hanjun Guo <hanjun.guo@linaro.org>, Marc Zyngier <maz@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] clocksource/drivers/arm_arch_timer: Mark hisi_161010101_oem_info const
Date: Mon, 6 May 2024 09:03:03 +0800 [thread overview]
Message-ID: <ead7324b-3cc1-15da-d80f-ef5ea1bec218@huawei.com> (raw)
In-Reply-To: <20240502233447.420888-1-swboyd@chromium.org>
On 2024/5/3 7:34, Stephen Boyd wrote:
> This isn't modified at runtime. Mark it const so it can move to
> read-only data.
>
> Cc: dann frazier <dann.frazier@canonical.com>
> Cc: Hanjun Guo <hanjun.guo@linaro.org>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
> drivers/clocksource/arm_arch_timer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index 8d4a52056684..5bb43cc1a8df 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
> @@ -331,7 +331,7 @@ static u64 notrace hisi_161010101_read_cntvct_el0(void)
> return __hisi_161010101_read_reg(cntvct_el0);
> }
>
> -static struct ate_acpi_oem_info hisi_161010101_oem_info[] = {
> +static const struct ate_acpi_oem_info hisi_161010101_oem_info[] = {
> /*
> * Note that trailing spaces are required to properly match
> * the OEM table information.
Looks good to me,
Reviewed-by: Hanjun Guo <guohanjun@huawei.com>
prev parent reply other threads:[~2024-05-06 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 23:34 [PATCH] clocksource/drivers/arm_arch_timer: Mark hisi_161010101_oem_info const Stephen Boyd
2024-05-06 1:03 ` Hanjun Guo [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=ead7324b-3cc1-15da-d80f-ef5ea1bec218@huawei.com \
--to=guohanjun@huawei.com \
--cc=daniel.lezcano@linaro.org \
--cc=dann.frazier@canonical.com \
--cc=hanjun.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=patches@lists.linux.dev \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).