From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18 1/1] arch/arm64/kvm/hyp/nvhe/pkvm.c:238:1: sparse: sparse: symbol 'vm_table_lock' was not declared. Should it be static?
Date: Fri, 06 Feb 2026 05:14:43 +0800 [thread overview]
Message-ID: <202602060552.R9rtCNB0-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18
head: 876b4b17abb486d9dc2805798495e0fccbde8d29
commit: 71a9fd9aad9776fed5877c6f50633b92cc6193fe [1/1] ANDROID: KVM: arm64: Handle guest FF-A share/lend/reclaim
config: arm64-randconfig-r134-20260205 (https://download.01.org/0day-ci/archive/20260206/202602060552.R9rtCNB0-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260206/202602060552.R9rtCNB0-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/202602060552.R9rtCNB0-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/arm64/kvm/hyp/nvhe/pkvm.c:238:1: sparse: sparse: symbol 'vm_table_lock' was not declared. Should it be static?
vim +/vm_table_lock +238 arch/arm64/kvm/hyp/nvhe/pkvm.c
a1ec5c70d3f63d Fuad Tabba 2022-11-10 236
4f1b201bef3e4d Will Deacon 2023-06-30 237 /* Rwlock for protecting state related to the VM table. */
4f1b201bef3e4d Will Deacon 2023-06-30 @238 DEFINE_HYP_RWLOCK(vm_table_lock);
a1ec5c70d3f63d Fuad Tabba 2022-11-10 239
:::::: The code at line 238 was first introduced by commit
:::::: 4f1b201bef3e4dbb6be6e30fb7f74ca90a0545fb ANDROID: KVM: arm64: Convert pKVM 'vm_table_lock' to an rwlock
:::::: TO: Will Deacon <willdeacon@google.com>
:::::: CC: Fuad Tabba <tabba@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-05 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=202602060552.R9rtCNB0-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.