From: Nathan Chancellor <nathan@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
linux-kbuild@vger.kernel.org, linux-efi@vger.kernel.org,
loongarch@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] kbuild: Add KBUILD_VMLINUX_LIBS_PRELINK
Date: Fri, 21 Nov 2025 18:35:51 -0700 [thread overview]
Message-ID: <20251122013551.GA3928114@ax162> (raw)
In-Reply-To: <20251119042708.27658-1-yangtiezhu@loongson.cn>
On Wed, Nov 19, 2025 at 12:27:08PM +0800, Tiezhu Yang wrote:
...
> index 433849ff7529..e72d3254b93f 100755
> --- a/scripts/link-vmlinux.sh
> +++ b/scripts/link-vmlinux.sh
> @@ -61,12 +61,11 @@ vmlinux_link()
> shift
>
> if is_enabled CONFIG_LTO_CLANG || is_enabled CONFIG_X86_KERNEL_IBT; then
> - # Use vmlinux.o instead of performing the slow LTO link again.
Why is this comment getting removed?
> objs=vmlinux.o
> - libs=
> + libs="${KBUILD_VMLINUX_LIBS_PRELINK}"
> else
> objs=vmlinux.a
> - libs="${KBUILD_VMLINUX_LIBS}"
> + libs="${KBUILD_VMLINUX_LIBS} ${KBUILD_VMLINUX_LIBS_PRELINK}"
> fi
>
> if is_enabled CONFIG_GENERIC_BUILTIN_DTB; then
> --
> 2.42.0
>
next prev parent reply other threads:[~2025-11-22 1:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 4:27 [PATCH v1] kbuild: Add KBUILD_VMLINUX_LIBS_PRELINK Tiezhu Yang
2025-11-21 7:01 ` Nathan Chancellor
2025-11-21 18:42 ` Josh Poimboeuf
2025-11-22 0:01 ` Nathan Chancellor
2025-11-22 1:35 ` Nathan Chancellor [this message]
2025-11-22 11:26 ` Tiezhu Yang
2025-11-23 21:15 ` Nathan Chancellor
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=20251122013551.GA3928114@ax162 \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
--cc=yangtiezhu@loongson.cn \
/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).