From: Nathan Chancellor <nathan@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Huacai Chen <chenhuacai@kernel.org>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix objtool warnings if LTO is enabled for LoongArch
Date: Thu, 14 Aug 2025 16:01:37 -0700 [thread overview]
Message-ID: <20250814230137.GA2247447@ax162> (raw)
In-Reply-To: <20250812132716.1465-1-yangtiezhu@loongson.cn>
On Tue, Aug 12, 2025 at 09:27:14PM +0800, Tiezhu Yang wrote:
> The patch #1 should be a preparation for patch #2, that is to say,
> the patch #2 is dependent on the patch #1, otherwise there is build
> error if LTO is enabled after only applying patch #2.
Thanks, these two patches do indeed resolve most of the warnings that I
see.
Tested-by: Nathan Chancellor <nathan@kernel.org>
> With this series, most of warnings have been silenced, only remains
> the following warning by now, it needs more analysis:
>
> vmlinux.o: warning: objtool: __efistub_efi_boot_kernel() falls through
> to next function __efistub_exit_boot_func()
Yes, I do see this one too. Odd, as efi_boot_kernel() ends in a
__noreturn function...
Cheers,
Nathan
next prev parent reply other threads:[~2025-08-14 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 13:27 [PATCH 0/2] Fix objtool warnings if LTO is enabled for LoongArch Tiezhu Yang
2025-08-12 13:27 ` [PATCH 1/2] objtool/LoongArch: Get table size correctly if LTO is enabled Tiezhu Yang
2025-08-12 13:27 ` [PATCH 2/2] LoongArch: Pass annotate-tablejump option " Tiezhu Yang
2025-08-14 23:01 ` Nathan Chancellor [this message]
2025-08-16 14:59 ` [PATCH 0/2] Fix objtool warnings if LTO is enabled for LoongArch Huacai Chen
2025-08-18 3:48 ` Tiezhu Yang
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=20250814230137.GA2247447@ax162 \
--to=nathan@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.