From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [kvm:queue 136/148] arch/x86/kvm/vmx/vmx.c:440:11: sparse: sparse: symbol 'vmx_uret_msrs_list' was not declared. Should it be
Date: Mon, 28 Sep 2020 23:37:12 +0800 [thread overview]
Message-ID: <202009282300.GKb6ot6E%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
tree: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
head: 0c899c25d754ae386940f0e1b86b31d3921480b6
commit: 14a61b642de9e5612f091b3295da6d0c89449a49 [136/148] KVM: VMX: Rename "vmx_msr_index" to "vmx_uret_msrs_list"
config: i386-randconfig-s001-20200928 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-201-g24bdaac6-dirty
# https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?id=14a61b642de9e5612f091b3295da6d0c89449a49
git remote add kvm https://git.kernel.org/pub/scm/virt/kvm/kvm.git
git fetch --no-tags kvm queue
git checkout 14a61b642de9e5612f091b3295da6d0c89449a49
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> arch/x86/kvm/vmx/vmx.c:440:11: sparse: sparse: symbol 'vmx_uret_msrs_list' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
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: 37122 bytes --]
next reply other threads:[~2020-09-28 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 15:37 kernel test robot [this message]
2020-09-28 15:37 ` [RFC PATCH kvm] KVM: VMX: vmx_uret_msrs_list[] can be static kernel test robot
2020-09-28 15:37 ` kernel test robot
2020-09-30 0:17 ` Sean Christopherson
2020-09-30 0:17 ` Sean Christopherson
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=202009282300.GKb6ot6E%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.