From: Nicolas Schier <nicolas@fjasle.eu>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
llvm@lists.linux.dev
Subject: Re: [PATCH 00/27] kbuild: yet another series of cleanups (modpost and LTO)
Date: Tue, 26 Apr 2022 22:10:55 +0200 [thread overview]
Message-ID: <YmhRz1SEjpEU8Nty@fjasle.eu> (raw)
In-Reply-To: <20220424190811.1678416-1-masahiroy@kernel.org>
On Mon, Apr 25, 2022 at 04:07:44AM +0900 Masahiro Yamada wrote:
> This is the third batch of cleanups in this development cycle.
>
> This weekend, I wrote up the code I have been planning.
>
> After a bunch of modpost refactoring, I got rid of the ugly code
> in Makefiles.
>
> With this, Kbuild will get back much simpler and cleaner.
>
Hi Masahiro,
I tried applying the patch set onto your kbuild and
kbuild-fixes-v5.18, but it didn't apply. Can you give me
a hint on your commit base?
Kind regards,
Nicolas
>
> Masahiro Yamada (27):
> modpost: use snprintf() instead of sprintf() for safety
> modpost: do not write out any file when error occurred
> modpost: remove stale comment about sym_add_exported()
> modpost: add a separate error for exported symbols without definition
> modpost: retrieve the module dependency and CRCs in check_exports()
> modpost: use bool type where appropriate
> modpost: import include/linux/list.h
> modpost: traverse modules in order
> modpost: add sym_add_unresolved() helper
> modpost: traverse unresolved symbols in order
> modpost: use doubly linked list for dump_lists
> modpost: move struct namespace_list to modpost.c
> modpost: traverse the namespace_list in order
> modpost: dump Module.symvers in the same order of modules.order
> modpost: move static EXPORT_SYMBOL check to check_exports()
> modpost: make multiple export error
> modpost: make sym_add_exported() always allocate a new symbol
> modpost: make sym_add_exported() a void function
> modpost: use hlist for hash table implementation
> modpost: mitigate false-negatives for static EXPORT_SYMBOL checks
> kbuild: record symbol versions in *.cmd files
> kbuild: generate a list of objects in vmlinux
> modpost: retrieve symbol versions by parsing *.cmd files
> modpost: generate linker script to collect symbol versions
> kbuild: embed symbol versions at final link of vmlinux or modules
> kbuild: stop generating *.symversions
> kbuild: do not create *.prelink.o for Clang LTO or IBT
>
> .gitignore | 1 +
> Makefile | 1 +
> scripts/Kbuild.include | 4 +
> scripts/Makefile.build | 107 ++------
> scripts/Makefile.lib | 7 -
> scripts/Makefile.modfinal | 6 +-
> scripts/Makefile.modpost | 9 +-
> scripts/link-vmlinux.sh | 38 ++-
> scripts/mod/file2alias.c | 2 -
> scripts/mod/list.h | 336 ++++++++++++++++++++++++
> scripts/mod/modpost.c | 529 +++++++++++++++++++++++---------------
> scripts/mod/modpost.h | 27 +-
> 12 files changed, 731 insertions(+), 336 deletions(-)
> create mode 100644 scripts/mod/list.h
>
> --
> 2.32.0
--
epost|xmpp: nicolas@fjasle.eu irc://oftc.net/nsc
↳ gpg: 18ed 52db e34f 860e e9fb c82b 7d97 0932 55a0 ce7f
-- frykten for herren er opphav til kunnskap --
next prev parent reply other threads:[~2022-04-26 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 19:07 [PATCH 00/27] kbuild: yet another series of cleanups (modpost and LTO) Masahiro Yamada
2022-04-24 19:08 ` [PATCH 21/27] kbuild: record symbol versions in *.cmd files Masahiro Yamada
2022-04-27 20:08 ` Nicolas Schier
2022-04-24 19:08 ` [PATCH 23/27] modpost: retrieve symbol versions by parsing " Masahiro Yamada
2022-04-24 19:08 ` [PATCH 27/27] kbuild: do not create *.prelink.o for Clang LTO or IBT Masahiro Yamada
2022-04-28 3:30 ` Nicolas Schier
2022-04-28 4:38 ` Masahiro Yamada
2022-04-28 6:59 ` Nicolas Schier
2022-04-26 20:10 ` Nicolas Schier [this message]
2022-04-27 3:18 ` [PATCH 00/27] kbuild: yet another series of cleanups (modpost and LTO) Masahiro Yamada
2022-05-01 7:11 ` 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=YmhRz1SEjpEU8Nty@fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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).