From: Sasha Levin <sashal@kernel.org>
To: Loic <hackurx@opensec.fr>
Cc: stable@vger.kernel.org, Julia.Lawall@lip6.fr,
keescook@chromium.org, lee.jones@linaro.org
Subject: Re: [PATCH] mfd: max8925-i2c: Drop unnecessary static
Date: Mon, 5 Nov 2018 18:46:02 -0500 [thread overview]
Message-ID: <20181105234602.GU194472@sasha-vm> (raw)
In-Reply-To: <20181020200741.9a5fe729f49b847e729a9575@opensec.fr>
On Sat, Oct 20, 2018 at 08:07:41PM +0200, Loic wrote:
>Hello,
>
>Please picked up this patch for linux 4.4 and 4.9.
>Compiled/tested without problem.
>
>[ Upstream commit 0953075112d7626474b0bb88690f5f1ab93ec803 ]
>
>From: Julia Lawall <Julia.Lawall@lip6.fr>
>Date: Thu, 4 May 2017 22:10:54 +0200
>Subject: [PATCH] mfd: max8925-i2c: Drop unnecessary static
>
>Drop static on a local variable, when the variable is initialized before
>any use, on every possible execution path through the function. The static
>has no benefit, and dropping it reduces the code size.
>
>The semantic patch that fixes this problem is as follows:
>(http://coccinelle.lip6.fr/)
>
>// <smpl>
>@bad exists@
>position p;
>identifier x;
>type T;
>@@
>
>static T x@p;
>...
>x = <+...x...+>
>
>@@
>identifier x;
>expression e;
>type T;
>position p != bad.p;
>@@
>
>-static
> T x@p;
> ... when != x
> when strict
>?x = e;
>// </smpl>
>
>The change in code size is indicates by the following output from the size
>command.
>
>before:
> text data bss dec hex filename
> 2579 240 16 2835 b13 drivers/mfd/max8925-i2c.o
>
>after:
> text data bss dec hex filename
> 2531 240 8 2779 adb drivers/mfd/max8925-i2c.o
>
>Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>Acked-by: Kees Cook <keescook@chromium.org>
>Signed-off-by: Lee Jones <lee.jones@linaro.org>
This doesn't really fix anything, not even a harmless warning, so I'd
rather leave it out.
--
Thanks,
Sasha
prev parent reply other threads:[~2018-11-06 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 18:07 [PATCH] mfd: max8925-i2c: Drop unnecessary static Loic
2018-11-05 23:46 ` Sasha Levin [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=20181105234602.GU194472@sasha-vm \
--to=sashal@kernel.org \
--cc=Julia.Lawall@lip6.fr \
--cc=hackurx@opensec.fr \
--cc=keescook@chromium.org \
--cc=lee.jones@linaro.org \
--cc=stable@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