From: Wei Liu <wei.liu@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wei Liu <wei.liu@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the hyperv tree
Date: Mon, 7 Aug 2023 04:46:53 +0000 [thread overview]
Message-ID: <ZNB3PXgIBvJhiEu1@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20230807142238.50616687@canb.auug.org.au>
On Mon, Aug 07, 2023 at 02:22:38PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the hyperv tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/pci/controller/pci-hyperv.o: warning: objtool: .altinstr_replacement+0x0: weirdly overlapping alternative! 11 != 6
> drivers/hv/hv_balloon.o: warning: objtool: .altinstr_replacement+0x0: weirdly overlapping alternative! 11 != 6
> drivers/hv/hv_vmbus.o: warning: objtool: .altinstr_replacement+0x3: weirdly overlapping alternative! 10 != 5
> vmlinux.o: warning: objtool: .altinstr_replacement+0x633: weirdly overlapping alternative! 11 != 6
> incomplete ORC unwind tables in file: vmlinux
> Failed to sort kernel tables
>
> I have no idea what caused this.
>
/me scratches head.
> I have used the hyperv tree from next-20230804 for today.
I've reverted that series from my tree. Thanks for the heads up.
Thanks,
Wei.
next prev parent reply other threads:[~2023-08-07 4:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 4:22 linux-next: build failure after merge of the hyperv tree Stephen Rothwell
2023-08-07 4:46 ` Wei Liu [this message]
2023-08-08 2:35 ` Dexuan-Linux Cui
-- strict thread matches above, loose matches on Subject: below --
2024-03-12 4:18 Stephen Rothwell
2024-03-12 5:25 ` Wei Liu
2023-04-18 17:31 broonie
2023-04-18 18:34 ` Wei Liu
2023-04-18 17:00 broonie
2023-04-18 17:06 ` Mark Brown
2023-04-18 17:24 ` Wei Liu
2020-06-02 7:35 Stephen Rothwell
2020-03-31 6:23 Stephen Rothwell
2020-04-01 17:45 ` Wei Liu
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=ZNB3PXgIBvJhiEu1@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).