All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Colin King <colin.king@canonical.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcma: make arrays pwr_info_offset and sprom_sizes static const, shrinks object size
Date: Fri, 13 Sep 2019 13:45:05 +0000	[thread overview]
Message-ID: <20190913134505.E0AC7601C3@smtp.codeaurora.org> (raw)
In-Reply-To: <20190905162049.14333-1-colin.king@canonical.com>

Colin King <colin.king@canonical.com> wrote:

> From: Colin Ian King <colin.king@canonical.com>
> 
> Arrays pwr_info_offset and sprom_sizes can be make static const rather
> than populating them on the stack. Shrinks object size by 236 bytes.
> 
> Before:
>    text	   data	    bss	    dec	    hex	filename
>   11300	   1320	     64	  12684	   318c	drivers/bcma/sprom.o
> 
> After:
>    text	   data	    bss	    dec	    hex	filename
>   10904	   1480	     64	  12448	   30a0	drivers/bcma/sprom.o
> 
> (gcc version 9.2.1, amd64)
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>

Patch applied to wireless-drivers-next.git, thanks.

c57391f41572 bcma: make arrays pwr_info_offset and sprom_sizes static const, shrinks object size

-- 
https://patchwork.kernel.org/patch/11133647/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Colin King <colin.king@canonical.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcma: make arrays pwr_info_offset and sprom_sizes static const, shrinks object size
Date: Fri, 13 Sep 2019 13:45:05 +0000 (UTC)	[thread overview]
Message-ID: <20190913134505.E0AC7601C3@smtp.codeaurora.org> (raw)
In-Reply-To: <20190905162049.14333-1-colin.king@canonical.com>

Colin King <colin.king@canonical.com> wrote:

> From: Colin Ian King <colin.king@canonical.com>
> 
> Arrays pwr_info_offset and sprom_sizes can be make static const rather
> than populating them on the stack. Shrinks object size by 236 bytes.
> 
> Before:
>    text	   data	    bss	    dec	    hex	filename
>   11300	   1320	     64	  12684	   318c	drivers/bcma/sprom.o
> 
> After:
>    text	   data	    bss	    dec	    hex	filename
>   10904	   1480	     64	  12448	   30a0	drivers/bcma/sprom.o
> 
> (gcc version 9.2.1, amd64)
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>

Patch applied to wireless-drivers-next.git, thanks.

c57391f41572 bcma: make arrays pwr_info_offset and sprom_sizes static const, shrinks object size

-- 
https://patchwork.kernel.org/patch/11133647/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2019-09-13 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 16:20 [PATCH] bcma: make arrays pwr_info_offset and sprom_sizes static const, shrinks object size Colin King
2019-09-05 16:20 ` Colin King
2019-09-13 13:45 ` Kalle Valo [this message]
2019-09-13 13:45   ` Kalle Valo

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=20190913134505.E0AC7601C3@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=colin.king@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.