From: Guenter Roeck <linux@roeck-us.net>
To: Colin Ian King <colin.king@canonical.com>
Cc: Rudolf Marek <r.marek@assembler.cz>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: hwmon: (w83793): make const array watchdog_minors static, reduces object code size
Date: Sun, 1 Oct 2017 07:16:25 -0700 [thread overview]
Message-ID: <20171001141625.GA32284@roeck-us.net> (raw)
In-Reply-To: <20170922143620.13780-1-colin.king@canonical.com>
On Fri, Sep 22, 2017 at 03:36:20PM +0100, Colin Ian King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Don't populate const array watchdog_minors on the stack, instead make it
> static. Makes the object code smaller by over 350 bytes:
>
> Before:
> text data bss dec hex filename
> 48019 38144 256 86419 15193 drivers/hwmon/w83793.o
>
> After:
> text data bss dec hex filename
> 47574 38232 256 86062 1502e drivers/hwmon/w83793.o
>
> (gcc 6.3.0, x86-64)
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied to hwmon-next.
Thanks,
Guenter
> ---
> drivers/hwmon/w83793.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/w83793.c b/drivers/hwmon/w83793.c
> index dab5c515d5a3..5ba9d9f1daa1 100644
> --- a/drivers/hwmon/w83793.c
> +++ b/drivers/hwmon/w83793.c
> @@ -1676,7 +1676,9 @@ static int w83793_probe(struct i2c_client *client,
> const struct i2c_device_id *id)
> {
> struct device *dev = &client->dev;
> - const int watchdog_minors[] = { WATCHDOG_MINOR, 212, 213, 214, 215 };
> + static const int watchdog_minors[] = {
> + WATCHDOG_MINOR, 212, 213, 214, 215
> + };
> struct w83793_data *data;
> int i, tmp, val, err;
> int files_fan = ARRAY_SIZE(w83793_left_fan) / 7;
prev parent reply other threads:[~2017-10-01 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 14:36 [PATCH] hwmon: (w83793): make const array watchdog_minors static, reduces object code size Colin King
2017-10-01 14:16 ` Guenter Roeck [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=20171001141625.GA32284@roeck-us.net \
--to=linux@roeck-us.net \
--cc=colin.king@canonical.com \
--cc=jdelvare@suse.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r.marek@assembler.cz \
/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