From: Viresh Kumar <viresh.kumar@linaro.org>
To: Xueqin Luo <luoxueqin@kylinos.cn>
Cc: rafael@kernel.org, zhongqiu.han@oss.qualcomm.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] cpufreq: sparc-us2e: fix frequency table index copy-paste error
Date: Mon, 31 Aug 2026 11:17:49 +0530 [thread overview]
Message-ID: <apUVhZnScyPdP_t_@vireshk-B250M-D3H> (raw)
In-Reply-To: <20260831054438.3632612-1-luoxueqin@kylinos.cn>
On 31-08-26, 13:44, Xueqin Luo wrote:
> In us2e_freq_cpu_init(), the last two frequency writes both use
> index [2] instead of [3] and [4] respectively, and the terminator
> uses [3] instead of [5]. This is a copy-paste error where the index
> was not incremented, causing the divider-6 and divider-8 entries to
> overwrite the already-written divider-4 entry.
>
> As a result, only three frequency steps (div 1, 2, and 4) are actually
> available to the cpufreq core, while the intended dividers 6 and 8 are
> silently lost. The struct us2e_freq_percpu_info::table[6] has room for
> 5 entries plus a terminator, matching the 5 hardware dividers.
>
> Fix the indices so all five frequency steps are correctly populated:
> table[0]=div1, table[1]=div2, table[2]=div4, table[3]=div6,
> table[4]=div8, table[5]=TABLE_END.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Xueqin Luo <luoxueqin@kylinos.cn>
> ---
> v2: Correct commit message per Zhongqiu Han's review, no code change.
> ---
> drivers/cpufreq/sparc-us2e-cpufreq.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
Applied. Thanks.
--
viresh
prev parent reply other threads:[~2026-08-31 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 5:44 [PATCH v2] cpufreq: sparc-us2e: fix frequency table index copy-paste error Xueqin Luo
2026-08-31 5:47 ` Viresh Kumar [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=apUVhZnScyPdP_t_@vireshk-B250M-D3H \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luoxueqin@kylinos.cn \
--cc=rafael@kernel.org \
--cc=zhongqiu.han@oss.qualcomm.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