From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Dongxu Sun <sundongxu3@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 3121/3121] arch/arm64/kvm/vgic/vgic-v4.c:258: warning: Function parameter or member 'vcpu' not described in 'kvm_vgic_get_vcpu_vpeid'
Date: Fri, 15 Aug 2025 23:14:58 +0200 [thread overview]
Message-ID: <202508152341.eaFFPaF8-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: ba1cb5cd91532ae2be2a0db5d153889580453f5f
commit: f1aaf830a93ca4915d9ffe39168f5eda472918a3 [3121/3121] KVM: arm64: GICv4.1: Add support for MBIGEN save/restore
config: arm64-randconfig-2001-20250814 (https://download.01.org/0day-ci/archive/20250815/202508152341.eaFFPaF8-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250815/202508152341.eaFFPaF8-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/202508152341.eaFFPaF8-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/arm64/kvm/vgic/vgic-v4.c:258: warning: Function parameter or member 'vcpu' not described in 'kvm_vgic_get_vcpu_vpeid'
vim +258 arch/arm64/kvm/vgic/vgic-v4.c
251
252 /**
253 * kvm_vgic_get_vcpu_vpeid - Get the VCPU's vpeid
254 *
255 * The vtimer mbigen needs the vcpu vpeid info which will resident.
256 */
257 u16 kvm_vgic_get_vcpu_vpeid(struct kvm_vcpu *vcpu)
> 258 {
259 return vcpu->arch.vgic_cpu.vgic_v3.its_vpe.vpe_id;
260 }
261
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-15 21:15 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=202508152341.eaFFPaF8-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sundongxu3@huawei.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.