From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Ellerman <mpe@ellerman.id.au>,
maddy@linux.ibm.com
Subject: Build Warnings at arch/powerpc/
Date: Tue, 4 Mar 2025 10:42:53 +0530 [thread overview]
Message-ID: <8c4c3fc2-2bd7-4148-af68-2f504d6119e0@linux.ibm.com> (raw)
Greetings!!
Observing build warnings with linux-next and powerpc repo's. Issue is
currently not seen on mainline yet.
PPC Repo:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git merge
branch
PPC Kernel Version: 6.14.0-rc4-g1304f486dbf1
next Repo:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
master branch
next Kernel Version: 6.14.0-rc5-next-20250303
On linux-next kernel issue got introduced b/w next-20250227 and
next-20250303
Build Warnings:
arch/powerpc/kvm/book3s_hv_rmhandlers.o: warning: objtool: .text+0xe84:
intra_function_call not a direct call
arch/powerpc/crypto/ghashp8-ppc.o: warning: objtool: .text+0x22c:
unannotated intra-function call
arch/powerpc/kernel/switch.o: warning: objtool: .text+0x4:
intra_function_call not a direct call
If you fix this issue, please add below tag.
Reported-By: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
Regards,
Venkat.
next reply other threads:[~2025-03-04 5:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 5:12 Venkat Rao Bagalkote [this message]
2025-03-04 6:13 ` Build Warnings at arch/powerpc/ Madhavan Srinivasan
2025-03-04 8:56 ` Christophe Leroy
2025-03-04 11:28 ` Madhavan Srinivasan
2025-03-04 12:38 ` Madhavan Srinivasan
2025-03-04 13:03 ` Venkat Rao Bagalkote
2025-03-04 13:13 ` Christophe Leroy
2025-03-04 15:44 ` Venkat Rao Bagalkote
2025-03-04 17:17 ` Christophe Leroy
2025-03-04 13:06 ` Christophe Leroy
2025-03-04 11:41 ` Venkat Rao Bagalkote
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=8c4c3fc2-2bd7-4148-af68-2f504d6119e0@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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