linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Rikard Falkeborn <rikard.falkeborn@gmail.com>,
	eric@anholt.net, f.fainelli@gmail.com, mturquette@baylibre.com,
	nsaenzjulienne@suse.de, rjui@broadcom.com, sbranden@broadcom.com,
	wahrenst@gmx.net
Cc: bcm-kernel-feedback-list@broadcom.com, linux-clk@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Rikard Falkeborn <rikard.falkeborn@gmail.com>
Subject: Re: [PATCH] clk: bcm2835: Constify struct debugfs_reg32
Date: Wed, 27 May 2020 00:10:13 -0700	[thread overview]
Message-ID: <159056341376.88029.8430380128281240784@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200508220238.4883-1-rikard.falkeborn@gmail.com>

Quoting Rikard Falkeborn (2020-05-08 15:02:38)
> bcm2835_debugfs_clock_reg32 is never changed and can therefore be made
> const.
> 
> This allows the compiler to put it in the text section instead of the
> data section.
> 
> Before:
>    text    data     bss     dec     hex filename
>   26598   16088      64   42750    a6fe drivers/clk/bcm/clk-bcm2835.o
> 
> After:
>    text    data     bss     dec     hex filename
>   26662   16024      64   42750    a6fe drivers/clk/bcm/clk-bcm2835.o
> 
> Signed-off-by: Rikard Falkeborn <rikard.falkeborn@gmail.com>
> ---

Applied to clk-next

      reply	other threads:[~2020-05-27  7:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 22:02 [PATCH] clk: bcm2835: Constify struct debugfs_reg32 Rikard Falkeborn
2020-05-27  7:10 ` Stephen Boyd [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=159056341376.88029.8430380128281240784@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=rikard.falkeborn@gmail.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=wahrenst@gmx.net \
    /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).