From: Nicholas Piggin <npiggin@gmail.com>
To: linux-kbuild@vger.kernel.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH v5 0/4] powerpc patches for new Kconfig language
Date: Wed, 30 May 2018 22:19:18 +1000 [thread overview]
Message-ID: <20180530121922.22122-1-npiggin@gmail.com> (raw)
This series of patches improves th powerpc kbuild system. The
motivation was to to be compatible with the new Kconfig scripting
language that Yamada-san has implemented here for merge:
https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/log/?h=kconfig
I have tested on top of that tree, powerpc now builds there.
To avoid build breakage, the first 3 patches must go before the
kconfig change, and the 4th patch must go after it.
v5 changes:
- Patch 4 update to syntax changed since kconfig-shell-v3 release.
- Patch 4 suggestions from Masahiro Yamada, remove unnecessary "OK"
output from check mprofile script, and fold CC_USING_MPROFILE_KERNEL
into CONFIG_MPROFILE_KERNEL.
- Reduce whitespace disturbance in patch 1.
Thanks,
Nick
Nicholas Piggin (4):
powerpc/kbuild: set default generic machine type for 32-bit compile
powerpc/kbuild: remove CROSS32 defines from top level powerpc Makefile
powerpc/kbuild: Use flags variables rather than overriding LD/CC/AS
powerpc/kbuild: move -mprofile-kernel check to Kconfig
arch/powerpc/Kconfig | 16 +------
arch/powerpc/Makefile | 44 ++++++++-----------
arch/powerpc/boot/Makefile | 16 ++++---
arch/powerpc/include/asm/module.h | 2 +-
arch/powerpc/kernel/module_64.c | 4 +-
arch/powerpc/kernel/trace/ftrace.c | 6 +--
arch/powerpc/kernel/vdso32/Makefile | 15 +++++--
.../tools/gcc-check-mprofile-kernel.sh | 13 +++---
scripts/recordmcount.pl | 18 +++++++-
9 files changed, 72 insertions(+), 62 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-30 12:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 12:19 Nicholas Piggin [this message]
2018-05-30 12:19 ` [PATCH v5 1/4] powerpc/kbuild: set default generic machine type for 32-bit compile Nicholas Piggin
2018-05-30 14:30 ` Masahiro Yamada
2018-05-30 14:32 ` Masahiro Yamada
2018-06-04 14:11 ` [v5, " Michael Ellerman
2018-05-30 12:19 ` [PATCH v5 2/4] powerpc/kbuild: remove CROSS32 defines from top level powerpc Makefile Nicholas Piggin
2018-06-04 14:11 ` [v5, " Michael Ellerman
2018-05-30 12:19 ` [PATCH v5 3/4] powerpc/kbuild: Use flags variables rather than overriding LD/CC/AS Nicholas Piggin
2018-05-30 14:34 ` Masahiro Yamada
2018-06-04 14:11 ` [v5, " Michael Ellerman
2018-05-30 12:19 ` [PATCH v5 4/4] powerpc/kbuild: move -mprofile-kernel check to Kconfig Nicholas Piggin
2018-05-30 14:39 ` [PATCH v5 0/4] powerpc patches for new Kconfig language Michael Ellerman
2018-05-30 14:57 ` Masahiro Yamada
2018-05-31 4:31 ` Michael Ellerman
2018-05-31 5:00 ` Masahiro Yamada
2018-05-31 11:51 ` Michael Ellerman
2018-05-31 13:08 ` Masahiro Yamada
2018-06-01 10:34 ` Michael Ellerman
2018-06-01 10:51 ` Masahiro Yamada
2018-06-01 13:22 ` Michael Ellerman
2018-06-02 4:53 ` 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=20180530121922.22122-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=segher@kernel.crashing.org \
--cc=yamada.masahiro@socionext.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 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).