From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Kees Cook <keescook@chromium.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-arch@vger.kernel.org
Subject: [PATCH 0/4] kbuild: fix and clean-up after avoiding kallsyms weak reference
Date: Mon, 20 May 2024 21:42:08 +0900 [thread overview]
Message-ID: <20240520124212.2351033-1-masahiroy@kernel.org> (raw)
I noticed a compile-time regression after commit 951bcae6c5a0
("kallsyms: Avoid weak references for kallsyms symbols").
1/4 fixes the unneeded kallsyms step 3.
2/4, 3/4, and 4/4 are follow-up cleanups.
Masahiro Yamada (4):
kbuild: avoid unneeded kallsyms step 3
kbuild: change scripts/mksysmap into sed script
kbuild: fix shortlog for AS in link-vmlinux.sh
kbuild: remove PROVIDE() for kallsyms symbols
include/asm-generic/vmlinux.lds.h | 19 ------------
kernel/kallsyms_internal.h | 5 ----
scripts/kallsyms.c | 6 ----
scripts/link-vmlinux.sh | 49 ++++++++++++++++---------------
scripts/mksysmap | 28 ++++--------------
5 files changed, 32 insertions(+), 75 deletions(-)
--
2.40.1
next reply other threads:[~2024-05-20 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 12:42 Masahiro Yamada [this message]
2024-05-20 12:42 ` [PATCH 1/4] kbuild: avoid unneeded kallsyms step 3 Masahiro Yamada
2024-05-20 12:42 ` [PATCH 2/4] kbuild: change scripts/mksysmap into sed script Masahiro Yamada
2024-05-20 12:42 ` [PATCH 3/4] kbuild: fix shortlog for AS in link-vmlinux.sh Masahiro Yamada
2024-05-20 12:42 ` [PATCH 4/4] kbuild: remove PROVIDE() for kallsyms symbols Masahiro Yamada
2024-05-21 7:12 ` kernel test robot
2024-05-22 10:15 ` 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=20240520124212.2351033-1-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
/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