From: Linus Walleij <linus.walleij@linaro.org>
To: "Gustavo A. R. Silva" <garsilva@embeddedor.com>
Cc: Alessandro Rubini <rubini@unipv.it>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: nomadik: abx500: constify gpio_chip structure
Date: Tue, 1 Aug 2017 09:59:11 +0200 [thread overview]
Message-ID: <CACRpkdZmUMRWZLak+3u3uGNyPDBmxqe6GH-aV2V1medoKmebBg@mail.gmail.com> (raw)
In-Reply-To: <20170711212929.GA1037@embeddedgus>
On Tue, Jul 11, 2017 at 11:29 PM, Gustavo A. R. Silva
<garsilva@embeddedor.com> wrote:
> This structure is only used to copy into another 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
> 17545 5376 0 22921 5989 drivers/pinctrl/nomadik/pinctrl-abx500.o
>
> after:
> bss dec hex filename
> 17273 5320 0 22593 5841 drivers/pinctrl/nomadik/pinctrl-abx500.o
>
> Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
Patch applied.
Yours,
Linus Walleij
prev parent reply other threads:[~2017-08-01 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 21:29 [PATCH] pinctrl: nomadik: abx500: constify gpio_chip structure Gustavo A. R. Silva
2017-08-01 7:59 ` Linus Walleij [this message]
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=CACRpkdZmUMRWZLak+3u3uGNyPDBmxqe6GH-aV2V1medoKmebBg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=garsilva@embeddedor.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@unipv.it \
/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).