From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 12/12] arch/arm64/kvm/pkvm.c:756:5: warning: no previous prototype for 'pkvm_enable_smc_forwarding'
Date: Fri, 17 Jul 2026 19:57:12 +0800 [thread overview]
Message-ID: <202607171934.slvzMeUv-lkp@intel.com> (raw)
Hi Nikita,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12
head: 1a1783c017b188c47740a5de7ffa05a4b75a2f09
commit: 128144da229a1de12ebe5bca87f607aa348c6ba9 [12/12] ANDROID: KVM: arm64: Add smc64 trap handling for protected guests
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20260717/202607171934.slvzMeUv-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260717/202607171934.slvzMeUv-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/202607171934.slvzMeUv-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/arm64/kvm/pkvm.c:756:5: warning: no previous prototype for 'pkvm_enable_smc_forwarding' [-Wmissing-prototypes]
756 | int pkvm_enable_smc_forwarding(struct file *kvm_file)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/pkvm_enable_smc_forwarding +756 arch/arm64/kvm/pkvm.c
755
> 756 int pkvm_enable_smc_forwarding(struct file *kvm_file)
757 {
758 struct kvm *host_kvm;
759
760 if (!file_is_kvm(kvm_file))
761 return -EINVAL;
762
763 if (!kvm_get_kvm_safe(kvm_file->private_data))
764 return -EINVAL;
765
766 host_kvm = kvm_file->private_data;
767 if (!host_kvm)
768 return -EINVAL;
769
770 host_kvm->arch.pkvm.smc_forwarded = true;
771
772 return 0;
773 }
774
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-17 11:57 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=202607171934.slvzMeUv-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.