[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOh2x=nDZpBaqjzO22k66Bb30mVEhAdy02EFDP9RDibA50Sx7A@mail.gmail.com>
Date: Mon, 25 Feb 2013 09:11:18 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Emilio López <emilio@...pez.com.ar>
Cc: rjw@...k.pl, shawn.guo@...aro.org, mark.langsdorf@...xeda.com,
linux-kernel@...r.kernel.org, cpufreq@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH] cpufreq: highbank: do not initialize array with a loop
On Sun, Feb 24, 2013 at 10:31 PM, Emilio López <emilio@...pez.com.ar> wrote:
> As uninitialized array members will be initialized to zero, we can
> avoid using a for loop by setting a value to it.
>
> Signed-off-by: Emilio López <emilio@...pez.com.ar>
> ---
> Note that I don't own any device using this driver, it has only been compile
> tested, but it shouldn't cause any issues.
>
> drivers/cpufreq/highbank-cpufreq.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/drivers/cpufreq/highbank-cpufreq.c b/drivers/cpufreq/highbank-cpufreq.c
> index 66e3a71..30d4ae1 100644
> --- a/drivers/cpufreq/highbank-cpufreq.c
> +++ b/drivers/cpufreq/highbank-cpufreq.c
> @@ -28,13 +28,9 @@
>
> static int hb_voltage_change(unsigned int freq)
> {
> - int i;
> - u32 msg[HB_CPUFREQ_IPC_LEN];
> + u32 msg[HB_CPUFREQ_IPC_LEN] = {HB_CPUFREQ_CHANGE_NOTE};
>
> - msg[0] = HB_CPUFREQ_CHANGE_NOTE;
> msg[1] = freq / 1000000;
I think this can also be part of the definition of array, isn't it?
So it would be something like:
u32 msg[HB_CPUFREQ_IPC_LEN] = {HB_CPUFREQ_CHANGE_NOTE, freq / 1000000};
> - for (i = 2; i < HB_CPUFREQ_IPC_LEN; i++)
> - msg[i] = 0;
>
> return pl320_ipc_transmit(msg);
> }
> --
> 1.8.2.rc0
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists