From: kernel test robot <lkp@intel.com>
To: Chenyi Qiang <chenyi.qiang@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [linux-next:master 1714/2566] x86_64/triple_fault_event_test.c:50:24: error: 'KVM_CAP_TRIPLE_FAULT_EVENT' undeclared; did you mean 'KVM_CAP_X86_TRIPLE_FAULT_EVENT'?
Date: Mon, 13 Jun 2022 18:52:41 +0800 [thread overview]
Message-ID: <202206131816.36JULzV7-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 6d0c806803170f120f8cb97b321de7bd89d3a791
commit: 30267b43c5b08260da7c76cacd28bf855b06ab93 [1714/2566] KVM: selftests: Add a test to get/set triple fault event
reproduce: make O=/tmp/kselftest -C tools/testing/selftests
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 6d0c806803170f120f8cb97b321de7bd89d3a791 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
x86_64/triple_fault_event_test.c: In function 'main':
>> x86_64/triple_fault_event_test.c:50:24: error: 'KVM_CAP_TRIPLE_FAULT_EVENT' undeclared (first use in this function); did you mean 'KVM_CAP_X86_TRIPLE_FAULT_EVENT'?
50 | .cap = KVM_CAP_TRIPLE_FAULT_EVENT,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| KVM_CAP_X86_TRIPLE_FAULT_EVENT
x86_64/triple_fault_event_test.c:50:24: note: each undeclared identifier is reported only once for each function it appears in
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-13 10:53 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=202206131816.36JULzV7-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenyi.qiang@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=pbonzini@redhat.com \
/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