From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nick Terrell <terrelln@fb.com>,
Nicolas Schier <nicolas@fjasle.eu>, Tom Rix <trix@redhat.com>,
llvm@lists.linux.dev
Subject: [PATCH 0/3] kbuild: detect objects shared among multiple modules
Date: Sun, 13 Nov 2022 20:15:22 +0900 [thread overview]
Message-ID: <20221113111525.3762483-1-masahiroy@kernel.org> (raw)
Commit 637a642f5ca5 ("zstd: Fixing mixed module-builtin objects")
only fixed zstd, but similar potential issues are remaining treewide.
My plan is to merge the first two in the next merge window
(to block new breakages), the last one after fixing warnings.
Masahiro Yamada (3):
kbuild: add kbuild-file macro
kbuild: warn objects shared among multiple modules
[pending] kbuild: make forbid sharing objects among multiple modules
scripts/Kbuild.include | 5 +++++
scripts/Makefile.asm-generic | 6 +++---
scripts/Makefile.build | 6 +-----
scripts/Makefile.clean | 5 +----
scripts/Makefile.dtbinst | 2 +-
scripts/Makefile.lib | 8 ++++----
scripts/Makefile.vmlinux_o | 5 +----
7 files changed, 16 insertions(+), 21 deletions(-)
--
2.34.1
next reply other threads:[~2022-11-13 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 11:15 Masahiro Yamada [this message]
2022-11-13 11:15 ` [PATCH 1/3] kbuild: add kbuild-file macro Masahiro Yamada
2022-11-17 20:47 ` Nicolas Schier
2022-11-18 0:45 ` Masahiro Yamada
2022-11-13 11:15 ` [PATCH 2/3] kbuild: warn objects shared among multiple modules Masahiro Yamada
2022-11-13 12:20 ` Masahiro Yamada
2022-11-13 11:15 ` [PATCH 3/3] [pending] kbuild: make forbid sharing objects " Masahiro Yamada
2022-11-22 6:27 ` Nicolas Schier
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=20221113111525.3762483-1-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=terrelln@fb.com \
--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