From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: SPEAr: Make read-only array sys_clk_src static
Date: Thu, 3 Nov 2022 14:49:31 +0000 [thread overview]
Message-ID: <ef637642-7d0f-66b8-2225-b6f8609f037e@gmail.com> (raw)
In-Reply-To: <20221103143807.tamhepos3cureoga@vireshk-i7>
On 03/11/2022 14:38, Viresh Kumar wrote:
> On 03-11-22, 14:36, Colin Ian King wrote:
>> Don't populate the read-only array sys_clk_src on the stack but instead
>> make it static and add in a missing const. Also makes the object code a
>> little smaller.
>>
>> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
>> ---
>> drivers/cpufreq/spear-cpufreq.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/cpufreq/spear-cpufreq.c b/drivers/cpufreq/spear-cpufreq.c
>> index 7d0d62a06bf3..c6fdf019dbde 100644
>> --- a/drivers/cpufreq/spear-cpufreq.c
>> +++ b/drivers/cpufreq/spear-cpufreq.c
>> @@ -39,7 +39,7 @@ static struct clk *spear1340_cpu_get_possible_parent(unsigned long newfreq)
>> * In SPEAr1340, cpu clk's parent sys clk can take input from
>> * following sources
>> */
>> - const char *sys_clk_src[] = {
>> + static const char * const sys_clk_src[] = {
>> "sys_syn_clk",
>> "pll1_clk",
>> "pll2_clk",
>
> Same questions from longhaul patch apply here too.
>
See answer in that patch :-)
But really, this is kind of basic C level stuff. I suggest reading K&R
2nd Edition, Section 4.6, last paragraph before exercise 4-11.
next prev parent reply other threads:[~2022-11-03 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 14:36 Colin Ian King
2022-11-03 14:38 ` Viresh Kumar
2022-11-03 14:49 ` Colin King (gmail) [this message]
2022-11-04 4:40 ` Viresh Kumar
2022-11-03 18:16 ` Rafael J. Wysocki
2022-11-04 4:51 ` Joe Perches
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=ef637642-7d0f-66b8-2225-b6f8609f037e@gmail.com \
--to=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
/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®