From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH 0/5] Register save/restore function build improvements
Date: Fri, 12 May 2017 01:56:47 +1000 [thread overview]
Message-ID: <20170511155652.8287-1-npiggin@gmail.com> (raw)
These are some minor improvements I came up when investigating
"orphan" sections (.sfpr currently is). For 4.13.
Nicholas Piggin (5):
powerpc/64: place sfpr section explicitly with the linker script
powerpc/64: do not link crtsavres.o in vmlinux
powerpc/64: do not link crtsaveres.o in boot
powerpc/64: do not create new section for save/restore functions
powerpc/64: Linker on-demand save/restore functions for modules
arch/powerpc/Makefile | 10 ++++++++++
arch/powerpc/boot/Makefile | 3 ++-
arch/powerpc/boot/crtsavres.S | 8 ++++----
arch/powerpc/kernel/vmlinux.lds.S | 8 ++++++++
arch/powerpc/lib/Makefile | 13 ++++++++++---
arch/powerpc/lib/crtsavres.S | 6 ++----
6 files changed, 36 insertions(+), 12 deletions(-)
--
2.11.0
next reply other threads:[~2017-05-11 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 15:56 Nicholas Piggin [this message]
2017-05-11 15:56 ` [PATCH 1/5] powerpc/64: place sfpr section explicitly with the linker script Nicholas Piggin
2017-05-30 9:11 ` [1/5] " Michael Ellerman
2017-05-11 15:56 ` [PATCH 2/5] powerpc/64: do not link crtsavres.o in vmlinux Nicholas Piggin
2017-05-11 15:56 ` [PATCH 3/5] powerpc/64: do not link crtsaveres.o in boot Nicholas Piggin
2017-05-12 14:19 ` kbuild test robot
2017-05-12 15:20 ` Nicholas Piggin
2017-05-11 15:56 ` [PATCH 4/5] powerpc/64: do not create new section for save/restore functions Nicholas Piggin
2017-05-11 15:56 ` [PATCH 5/5] powerpc/64: Linker on-demand sfpr functions for modules Nicholas Piggin
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=20170511155652.8287-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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 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.