From: Lee Jones <lee.jones@linaro.org>
To: Joe Perches <joe@perches.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: axp20x: Remove unnecessary const qualifier from axp20x_supplies[]
Date: Thu, 22 May 2014 17:08:56 +0100 [thread overview]
Message-ID: <20140522160856.GJ19747@lee--X1> (raw)
In-Reply-To: <1400774373.21099.1.camel@joe-AO725>
> > drivers/mfd/axp20x.c:159:3:
> > warning: initialization discards ‘const’ qualifier from pointer target type
> > .parent_supplies = axp20x_supplies,
> []
> > diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
> []
> > @@ -140,7 +140,7 @@ static const struct regmap_irq_chip axp20x_regmap_irq_chip = {
> > .init_ack_masked = true,
> > };
> >
> > -static const char * const axp20x_supplies[] = {
> > +static const char * axp20x_supplies[] = {
> > "acin",
> > "vin2",
> > "vin3",
>
> Perhaps you're doing this the wrong way round.
> Maybe this definition should change.
>
> include/linux/mfd/core.h: const char **parent_supplies;
Are you asking me, or telling me? :)
To be frank, I've never known what the double const means. Care to
enlighten?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-05-22 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 9:18 [PATCH] mfd: abx500-core: Remove unused function abx500_dump_all_banks() Lee Jones
2014-05-22 9:18 ` [PATCH] mfd: axp20x: Remove unnecessary const qualifier from axp20x_supplies[] Lee Jones
2014-05-22 15:59 ` Joe Perches
2014-05-22 16:08 ` Lee Jones [this message]
2014-05-22 16:45 ` Joe Perches
2014-05-23 11:43 ` Lee Jones
2014-05-22 9:18 ` [PATCH] mfd: max14577: Cast to architecture agnostic data type Lee Jones
2014-05-22 10:36 ` [PATCH] mfd: abx500-core: Remove unused function abx500_dump_all_banks() Jay Aurabind
2014-05-22 10:51 ` Lee Jones
2014-05-22 11:30 ` [PATCH v2] " Lee Jones
2014-05-22 22:27 ` Linus Walleij
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=20140522160856.GJ19747@lee--X1 \
--to=lee.jones@linaro.org \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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