From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Wei Liu <wei.liu@kernel•org>
Cc: Mukesh Rathor <mrathor@linux•microsoft.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the hyperv tree
Date: Mon, 20 Oct 2025 13:31:44 +1100 [thread overview]
Message-ID: <20251020133144.5e6e3d03@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 628 bytes --]
Hi all,
After merging the hyperv tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/hyperv/hv_init.c: In function 'hyperv_init':
arch/x86/hyperv/hv_init.c:558:17: error: implicit declaration of function 'hv_root_crash_init' [-Wimplicit-function-declaration]
558 | hv_root_crash_init();
| ^~~~~~~~~~~~~~~~~~
Caused by commit
60116744be53 ("x86/hyperv: Enable build of hypervisor crashdump collection files")
$ grep CONFIG_MSHV_ROOT .config
$
I have used the hyperv tree from next-20251017 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-10-20 2:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 2:31 Stephen Rothwell [this message]
2025-10-20 17:27 ` linux-next: build failure after merge of the hyperv tree Wei Liu
-- strict thread matches above, loose matches on Subject: below --
2025-05-06 7:26 Stephen Rothwell
2025-02-13 3:28 Stephen Rothwell
2025-02-13 22:58 ` Nuno Das Neves
2024-03-12 4:18 Stephen Rothwell
2024-03-12 5:25 ` Wei Liu
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=20251020133144.5e6e3d03@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mrathor@linux$(echo .)microsoft.com \
--cc=wei.liu@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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