public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Adam Ford <aford173@gmail.com>
To: u-boot@lists.denx.de
Cc: lukma@denx.de, pavel@ucw.cz, pali@kernel.org, lokeshvutla@ti.com,
	aford@beaconembedded.com, Adam Ford <aford173@gmail.com>
Subject: [PATCH V2 0/3] Make omap3 board functions static
Date: Fri, 25 Jun 2021 14:23:05 -0500	[thread overview]
Message-ID: <20210625192308.277136-1-aford173@gmail.com> (raw)

Several functions in omap3/board.c are only used in that file, and
two of them are only called when certain conditions are true in an
ifdef.  Rearange these functions to also be inside the ifdef and
make them static.

Before:

 text	   data	    bss	    dec	    hex	filename
  49998	   1057	   1888	  52943	   cecf	spl/u-boot-spl
 605972	  29244	  53020	 688236	  a806c	u-boot

After Patch 3/3:
   text	   data	    bss	    dec	    hex	filename
 605744	  29244	  52996	 687984	  a7f70	u-boot
  49918	   1057	   1888	  52863	   ce7f	spl/u-boot-spl

Adam Ford (3):
  arm: omap3: Make try_unlock_memory() static
  arm: omap3: Make secureworld_exit() static
  arm: omap3: Make secure_unlock_mem() static

 arch/arm/include/asm/arch-omap3/sys_proto.h |  2 --
 arch/arm/mach-omap2/omap3/board.c           | 21 +++++++++++----------
 2 files changed, 11 insertions(+), 12 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-06-25 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 19:23 Adam Ford [this message]
2021-06-25 19:23 ` [PATCH V2 1/3] arm: omap3: Make try_unlock_memory() static Adam Ford
2021-06-25 19:23 ` [PATCH V2 2/3] arm: omap3: Make secureworld_exit() static Adam Ford
2021-06-25 19:23 ` [PATCH V2 3/3] arm: omap3: Make secure_unlock_mem() static Adam Ford
2021-07-14  6:52 ` [PATCH V2 0/3] Make omap3 board functions static Lokesh Vutla

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=20210625192308.277136-1-aford173@gmail.com \
    --to=aford173@gmail.com \
    --cc=aford@beaconembedded.com \
    --cc=lokeshvutla@ti.com \
    --cc=lukma@denx.de \
    --cc=pali@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=u-boot@lists.denx.de \
    /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