From: Stephen Rothwell <sfr@canb.auug.org.au> To: Michael Ellerman <mpe@ellerman.id.au>, PowerPC <linuxppc-dev@lists.ozlabs.org> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>, Sathvika Vasireddy <sv@linux.ibm.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux Next Mailing List <linux-next@vger.kernel.org> Subject: linux-next: build warnings after merge of the powerpc-objtool tree Date: Fri, 25 Nov 2022 14:30:12 +1100 [thread overview] Message-ID: <20221125143012.6426c2b9@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 458 bytes --] Hi all, After merging the powerpc-objtool tree, today's linux-next build (powerpc pseries_le_defconfig) produced these warnings: arch/powerpc/kernel/head_64.o: warning: objtool: end_first_256B(): can't find starting instruction arch/powerpc/kernel/optprobes_head.o: warning: objtool: optprobe_template_end(): can't find starting instruction I have no idea what started this (they may have been there yesterday). -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au> To: Michael Ellerman <mpe@ellerman.id.au>, PowerPC <linuxppc-dev@lists.ozlabs.org> Cc: Linux Next Mailing List <linux-next@vger.kernel.org>, Sathvika Vasireddy <sv@linux.ibm.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: linux-next: build warnings after merge of the powerpc-objtool tree Date: Fri, 25 Nov 2022 14:30:12 +1100 [thread overview] Message-ID: <20221125143012.6426c2b9@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 458 bytes --] Hi all, After merging the powerpc-objtool tree, today's linux-next build (powerpc pseries_le_defconfig) produced these warnings: arch/powerpc/kernel/head_64.o: warning: objtool: end_first_256B(): can't find starting instruction arch/powerpc/kernel/optprobes_head.o: warning: objtool: optprobe_template_end(): can't find starting instruction I have no idea what started this (they may have been there yesterday). -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-11-25 3:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-25 3:30 Stephen Rothwell [this message] 2022-11-25 3:30 ` linux-next: build warnings after merge of the powerpc-objtool tree Stephen Rothwell 2022-11-29 15:13 ` Sathvika Vasireddy 2022-11-29 15:13 ` Sathvika Vasireddy 2022-11-29 15:28 ` Christophe Leroy 2022-11-29 15:28 ` Christophe Leroy 2022-11-30 11:51 ` Sathvika Vasireddy 2022-11-30 11:51 ` Sathvika Vasireddy 2022-12-06 10:14 ` Naveen N. Rao 2022-12-06 10:14 ` Naveen N. Rao
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=20221125143012.6426c2b9@canb.auug.org.au \ --to=sfr@canb.auug.org.au \ --cc=christophe.leroy@csgroup.eu \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-next@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mpe@ellerman.id.au \ --cc=sv@linux.ibm.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: linkBe 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.