linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrice CHOTARD <patrice.chotard@st.com>
To: "Gustavo A. R. Silva" <garsilva@embeddedor.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] pinctrl: st: constify gpio_chip structure
Date: Wed, 12 Jul 2017 07:03:29 +0000	[thread overview]
Message-ID: <c0a35f14-7c22-63f9-8bfa-2d88b5800fbd@st.com> (raw)
In-Reply-To: <20170711181519.GA20001@embeddedgus>

Hi Gustavo

On 07/11/2017 08:15 PM, Gustavo A. R. Silva wrote:
> This structure is only used to copy into other structure, so declare
> it as const.
> 
> This issue was detected using Coccinelle and the following semantic patch:
> 
> @r disable optional_qualifier@
> identifier i;
> position p;
> @@
> static struct gpio_chip i@p = { ... };
> 
> @ok@
> identifier r.i;
> expression e;
> position p;
> @@
> e = i@p;
> 
> @bad@
> position p != {r.p,ok.p};
> identifier r.i;
> struct gpio_chip e;
> @@
> e@i@p
> 
> @depends on !bad disable optional_qualifier@
> identifier r.i;
> @@
> static
> +const
>   struct gpio_chip i = { ... };
> 
> In the following log you can see a significant difference in the code size
> and data segment, hence in the dec segment. This log is the output
> of the size command, before and after the code change:
> 
> before:
>     text    data     bss     dec     hex filename
>    21671    3632     128   25431    6357 drivers/pinctrl/pinctrl-st.o
> 
> after:
>     text    data     bss     dec     hex filename
>    21366    3576     128   25070    61ee drivers/pinctrl/pinctrl-st.o
> 
> Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
> ---
>   drivers/pinctrl/pinctrl-st.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/pinctrl/pinctrl-st.c b/drivers/pinctrl/pinctrl-st.c
> index 3ae8066..5d4789d 100644
> --- a/drivers/pinctrl/pinctrl-st.c
> +++ b/drivers/pinctrl/pinctrl-st.c
> @@ -1442,7 +1442,7 @@ static void st_gpio_irqmux_handler(struct irq_desc *desc)
>   	chained_irq_exit(chip, desc);
>   }
>   
> -static struct gpio_chip st_gpio_template = {
> +static const struct gpio_chip st_gpio_template = {
>   	.request		= gpiochip_generic_request,
>   	.free			= gpiochip_generic_free,
>   	.get			= st_gpio_get,
> 

Acked-by: Patrice Chotard <patrice.chotard@st.com>

Thanks

  reply	other threads:[~2017-07-12  7:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 18:15 [PATCH] pinctrl: st: constify gpio_chip structure Gustavo A. R. Silva
2017-07-12  7:03 ` Patrice CHOTARD [this message]
2017-07-12 16:51   ` Gustavo A. R. Silva
2017-08-01 13:21 ` 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=c0a35f14-7c22-63f9-8bfa-2d88b5800fbd@st.com \
    --to=patrice.chotard@st.com \
    --cc=garsilva@embeddedor.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).