From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
llvm@lists.linux.dev, Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Michal Marek <michal.lkml@markovi.net>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>
Subject: [PATCH v7 0/8] kbuild: yet another series of cleanups
Date: Fri, 27 May 2022 19:01:47 +0900 [thread overview]
Message-ID: <20220527100155.1996314-1-masahiroy@kernel.org> (raw)
A couple errors have been reported since I applied v6.
I am sending v7.
Masahiro Yamada (8):
kbuild: replace $(linked-object) with CONFIG options
kbuild: do not create *.prelink.o for Clang LTO or IBT
parisc: fix the exit status of arch/parisc/nm
kbuild: check static EXPORT_SYMBOL* by script instead of modpost
kbuild: make built-in.a rule robust against too long argument error
kbuild: make *.mod rule robust against too long argument error
kbuild: add cmd_and_savecmd macro
kbuild: rebuild multi-object modules when objtool is updated
arch/parisc/Makefile | 2 +-
arch/parisc/nm | 12 +++++-
scripts/Kbuild.include | 10 ++++-
scripts/Makefile.build | 87 +++++++++++++++++---------------------
scripts/Makefile.lib | 7 ---
scripts/Makefile.modfinal | 5 +--
scripts/Makefile.modpost | 9 +---
scripts/check-local-export | 65 ++++++++++++++++++++++++++++
scripts/mod/modpost.c | 35 +--------------
9 files changed, 128 insertions(+), 104 deletions(-)
mode change 100644 => 100755 arch/parisc/nm
create mode 100755 scripts/check-local-export
--
2.32.0
next reply other threads:[~2022-05-27 10:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 10:01 Masahiro Yamada [this message]
2022-05-27 10:01 ` [PATCH v7 1/8] kbuild: replace $(linked-object) with CONFIG options Masahiro Yamada
2022-05-27 15:00 ` Josh Poimboeuf
2022-05-27 17:32 ` Nick Desaulniers
2022-05-28 2:32 ` Sedat Dilek
2022-05-28 7:10 ` Masahiro Yamada
2022-05-27 10:01 ` [PATCH v7 2/8] kbuild: do not create *.prelink.o for Clang LTO or IBT Masahiro Yamada
2022-05-27 15:31 ` Josh Poimboeuf
2022-05-27 10:01 ` [PATCH v7 3/8] parisc: fix the exit status of arch/parisc/nm Masahiro Yamada
2022-05-27 13:57 ` Helge Deller
2022-05-27 14:21 ` Masahiro Yamada
2022-05-27 10:01 ` [PATCH v7 4/8] kbuild: check static EXPORT_SYMBOL* by script instead of modpost Masahiro Yamada
2022-05-27 10:01 ` [PATCH v7 5/8] kbuild: make built-in.a rule robust against too long argument error Masahiro Yamada
2022-05-27 10:01 ` [PATCH v7 6/8] kbuild: make *.mod " Masahiro Yamada
2022-05-27 10:01 ` [PATCH v7 7/8] kbuild: add cmd_and_savecmd macro Masahiro Yamada
2022-05-27 10:01 ` [PATCH v7 8/8] kbuild: rebuild multi-object modules when objtool is updated Masahiro Yamada
2022-05-27 15:50 ` Josh Poimboeuf
2022-05-27 17:41 ` Masahiro Yamada
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=20220527100155.1996314-1-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=deller@gmx.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=trix@redhat.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