From: bpringlemeir@nbsps.com (Bill Pringlemeir)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: clk-imx6sl: Suppress duplicate const sparse warning
Date: Thu, 16 Jan 2014 12:06:36 -0500 [thread overview]
Message-ID: <87fvon6elf.fsf@nbsps.com> (raw)
In-Reply-To: <20140115065851.GC1914@S2101-09.ap.freescale.net> (Shawn Guo's message of "Wed, 15 Jan 2014 14:58:54 +0800")
> On Wed, Jan 15, 2014 at 02:19:34PM +0800, Liu Ying wrote:
>> There should be no duplicate const specifiers for those static
>> constant character string arrays defined for clock mux options.
>> Also, the arrays are only taken as the 5th argument for the
>> imx_clk_mux() function, which is in the type of 'const char
>> **parents'. So, let's remove the 2nd const specifier right
>> after 'char'.
>>
>> This patch fixes these sparse warnings:
>> arch/arm/mach-imx/clk-imx6sl.c:21:25: warning: duplicate const
[snip]
>> Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
>> ---
>> arch/arm/mach-imx/clk-imx6sl.c | 42 ++++++++++++++++++++--------------------
>> 1 file changed, 21 insertions(+), 21 deletions(-)
>>
>> diff --git a/arch/arm/mach-imx/clk-imx6sl.c b/arch/arm/mach-imx/clk-imx6sl.c
>> index c0c4ef5..9fad29a9 100644
>> --- a/arch/arm/mach-imx/clk-imx6sl.c
>> +++ b/arch/arm/mach-imx/clk-imx6sl.c
>>>> -18,27 +18,27 @@
>> #include "clk.h"
>> #include "common.h"
>>
>> -static const char const *step_sels[] = { "osc", "pll2_pfd2", };
> ...
>> +static const char *step_sels[] = { "osc", "pll2_pfd2", };
On 15 Jan 2014, shawn.guo at linaro.org wrote:
> So now we're getting the following checkpatch warning:
>
> WARNING: static const char * array should probably be static const char *
> const
>
> It was added into checkpatch.pl by commit cb710ec (scripts/checkpatch.pl:
> add warnings for static char that could be static const char). I'm not
> sure which warning we should ignore, the sparse or the checkpatch one.
I think both scripts/programs are right. There is a difference.
static const char const * step_sels[] = { "osc", "pll2_pfd2", }; /* dup */
static const char * const step_sels[] = { "osc", "pll2_pfd2", }; /* ok */
static char const * const step_sels[] = { "osc", "pll2_pfd2", }; /* ok */
I think that 'type const * const' is a const pointer to const data, but
'const type const *' is just a const pointer (with duplicate). The
patches have made the data non-const?
Fwiw,
Bill Pringlemeir.
next prev parent reply other threads:[~2014-01-16 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 6:19 [PATCH] ARM: imx: clk-imx6sl: Suppress duplicate const sparse warning Liu Ying
2014-01-15 6:58 ` Shawn Guo
2014-01-15 9:21 ` Joe Perches
2014-01-15 11:24 ` Shawn Guo
2014-01-16 17:06 ` Bill Pringlemeir [this message]
2014-01-16 17:28 ` Bill Pringlemeir
2014-01-17 5:44 ` Shawn Guo
2014-01-15 11:27 ` Shawn Guo
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=87fvon6elf.fsf@nbsps.com \
--to=bpringlemeir@nbsps.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).