From: Dexuan Cui <decui@microsoft.com>
To: kernel test robot <lkp@intel.com>, Tianyu Lan <Tianyu.Lan@microsoft.com>
Cc: "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
Linux Memory Management List <linux-mm@kvack.org>,
Wei Liu <wei.liu@kernel.org>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>
Subject: RE: [linux-next:master 11576/12208] arch/x86/kernel/cpu/mshyperv.c:407: undefined reference to `isolation_type_en_snp'
Date: Wed, 23 Aug 2023 17:06:48 +0000 [thread overview]
Message-ID: <SA1PR21MB1335B4EC7F7D51BB12F71C67BF1CA@SA1PR21MB1335.namprd21.prod.outlook.com> (raw)
In-Reply-To: <202308231805.RyYOycAU-lkp@intel.com>
> From: kernel test robot <lkp@intel.com>
> Sent: Wednesday, August 23, 2023 4:03 AM
> To: Tianyu Lan <Tianyu.Lan@microsoft.com>
> Cc: oe-kbuild-all@lists.linux.dev; Linux Memory Management List <linux-
> mm@kvack.org>; Wei Liu <wei.liu@kernel.org>; Dexuan Cui
> <decui@microsoft.com>; Michael Kelley (LINUX) <mikelley@microsoft.com>
> Subject: [linux-next:master 11576/12208]
> arch/x86/kernel/cpu/mshyperv.c:407: undefined reference to
> `isolation_type_en_snp'
The failure happens because we have CONFIG_HYPERVISOR_GUEST=y, but
CONFIG_HYPERV is not set. This has been fixed in the hyperv-next branch:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/log/?h=hyperv-next
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-next&id=86e619c922e616d8780833562a14a5bda329f0c3
The fix is not in linux-next's master branch (currently it's next-20230823) yet.
I believe tomorrow's linux-next would build successfully.
Thanks,
Dexuan
prev parent reply other threads:[~2023-08-23 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 11:02 kernel test robot
2023-08-23 17:06 ` Dexuan Cui [this message]
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=SA1PR21MB1335B4EC7F7D51BB12F71C67BF1CA@SA1PR21MB1335.namprd21.prod.outlook.com \
--to=decui@microsoft.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mikelley@microsoft.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wei.liu@kernel.org \
/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