From: Sean Christopherson <seanjc@google.com>
To: kernel test robot <lkp@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
oe-kbuild-all@lists.linux.dev, kvm@vger.kernel.org,
Robert Hu <robert.hu@intel.com>,
Farrah Chen <farrah.chen@intel.com>,
Danmei Wei <danmei.wei@intel.com>
Subject: Re: [kvm:guestmemfd 59/59] arch/s390/kvm/../../../virt/kvm/kvm_main.c:5517:14: error: 'KVM_TRACE_ENABLE' undeclared; did you mean 'KVM_PV_ENABLE'?
Date: Wed, 8 Nov 2023 12:19:56 -0800 [thread overview]
Message-ID: <ZUvtbInra7-Nypgq@google.com> (raw)
In-Reply-To: <202311090100.Zt0adRi9-lkp@intel.com>
On Thu, Nov 09, 2023, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/virt/kvm/kvm.git guestmemfd
> head: cd689ddd5c93ea177b28029d57c13e18b160875b
> commit: cd689ddd5c93ea177b28029d57c13e18b160875b [59/59] KVM: remove deprecated UAPIs
Paolo, I assume you force pushed to guestmemfd at some point at that this is no
longer an issue? I can't find the above object, and given the shortlog I'm guessing
it was a WIP thing unrelated to guest_memfd.
> config: s390-defconfig (https://download.01.org/0day-ci/archive/20231109/202311090100.Zt0adRi9-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231109/202311090100.Zt0adRi9-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202311090100.Zt0adRi9-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> arch/s390/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_dev_ioctl':
> >> arch/s390/kvm/../../../virt/kvm/kvm_main.c:5517:14: error: 'KVM_TRACE_ENABLE' undeclared (first use in this function); did you mean 'KVM_PV_ENABLE'?
> 5517 | case KVM_TRACE_ENABLE:
> | ^~~~~~~~~~~~~~~~
> | KVM_PV_ENABLE
> arch/s390/kvm/../../../virt/kvm/kvm_main.c:5517:14: note: each undeclared identifier is reported only once for each function it appears in
> >> arch/s390/kvm/../../../virt/kvm/kvm_main.c:5518:14: error: 'KVM_TRACE_PAUSE' undeclared (first use in this function)
> 5518 | case KVM_TRACE_PAUSE:
> | ^~~~~~~~~~~~~~~
> >> arch/s390/kvm/../../../virt/kvm/kvm_main.c:5519:14: error: 'KVM_TRACE_DISABLE' undeclared (first use in this function); did you mean 'KVM_PV_DISABLE'?
> 5519 | case KVM_TRACE_DISABLE:
> | ^~~~~~~~~~~~~~~~~
> | KVM_PV_DISABLE
>
>
> vim +5517 arch/s390/kvm/../../../virt/kvm/kvm_main.c
next prev parent reply other threads:[~2023-11-08 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 17:34 [kvm:guestmemfd 59/59] arch/s390/kvm/../../../virt/kvm/kvm_main.c:5517:14: error: 'KVM_TRACE_ENABLE' undeclared; did you mean 'KVM_PV_ENABLE'? kernel test robot
2023-11-08 20:19 ` Sean Christopherson [this message]
2023-11-08 20:31 ` Paolo Bonzini
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=ZUvtbInra7-Nypgq@google.com \
--to=seanjc@google.com \
--cc=danmei.wei@intel.com \
--cc=farrah.chen@intel.com \
--cc=kvm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=robert.hu@intel.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 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.