From: Wei Liu <wei.liu@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wei Liu <wei.liu@kernel.org>,
Nuno Das Neves <nunodasneves@linux.microsoft.com>,
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: Tue, 12 Mar 2024 05:25:46 +0000 [thread overview]
Message-ID: <Ze_nWnzKvw4kI_l5@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20240312151807.52478738@canb.auug.org.au>
On Tue, Mar 12, 2024 at 03:18:07PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the hyperv tree, today's linux-next build (i386 defconfig)
> failed like this:
>
> arch/x86/kernel/cpu/mshyperv.c:355:5: error: no previous prototype for 'hv_get_hypervisor_version' [-Werror=missing-prototypes]
> 355 | int hv_get_hypervisor_version(union hv_hypervisor_version_info *info)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
We noticed this as well. A fix has been sent out. I will update the tree
shortly.
Thanks,
Wei.
>
> Caused by commit
>
> 1634df06ea12 ("mshyperv: Introduce hv_get_hypervisor_version function")
>
> I have reverted that commit for today.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2024-03-12 5:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 4:18 linux-next: build failure after merge of the hyperv tree Stephen Rothwell
2024-03-12 5:25 ` Wei Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-07 4:22 Stephen Rothwell
2023-08-07 4:46 ` Wei Liu
2023-08-08 2:35 ` Dexuan-Linux Cui
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=Ze_nWnzKvw4kI_l5@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nunodasneves@linux.microsoft.com \
--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).