From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [joro:sev-es-client-v5.6-rc1 55/62] arch/x86/kernel/cpu/vmware.c:308:34: error: 'vmware_sev_es_hcall_prepare' undeclared here (not in a function)
Date: Wed, 12 Feb 2020 06:38:53 +0800 [thread overview]
Message-ID: <202002120637.CEmzITFf%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1812 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git sev-es-client-v5.6-rc1
head: 12f30df5e3e9037d01b41fa676867672c2e02519
commit: e195ed67479d7d2698326a31ea0ebef41570fc86 [55/62] x86/vmware: Add VMware specific handling for VMMCALL under SEV-ES
config: i386-randconfig-a003-20200212 (attached as .config)
compiler: gcc-6 (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
reproduce:
git checkout e195ed67479d7d2698326a31ea0ebef41570fc86
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> arch/x86/kernel/cpu/vmware.c:308:34: error: 'vmware_sev_es_hcall_prepare' undeclared here (not in a function)
.runtime.sev_es_hcall_prepare = vmware_sev_es_hcall_prepare,
^~~~~~~~~~~~~~~~~~~~~~~~~~~
>> arch/x86/kernel/cpu/vmware.c:309:33: error: 'vmware_sev_es_hcall_finish' undeclared here (not in a function)
.runtime.sev_es_hcall_finish = vmware_sev_es_hcall_finish,
^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/vmware_sev_es_hcall_prepare +308 arch/x86/kernel/cpu/vmware.c
301
302 const __initconst struct hypervisor_x86 x86_hyper_vmware = {
303 .name = "VMware",
304 .detect = vmware_platform,
305 .type = X86_HYPER_VMWARE,
306 .init.init_platform = vmware_platform_setup,
307 .init.x2apic_available = vmware_legacy_x2apic_available,
> 308 .runtime.sev_es_hcall_prepare = vmware_sev_es_hcall_prepare,
> 309 .runtime.sev_es_hcall_finish = vmware_sev_es_hcall_finish,
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 33542 bytes --]
reply other threads:[~2020-02-11 22:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202002120637.CEmzITFf%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.