All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-5.15-2025-10 1/1] arch/arm64/kvm/arm.c:493:15: warning: no previous prototype for 'kvm_arch_vcpu_get_ip'
Date: Fri, 25 Sep 2026 08:03:41 +0800	[thread overview]
Message-ID: <202609250707.v5In0Xad-lkp@intel.com> (raw)

Hi Sean,

FYI, the error/warning still remains.

tree:   https://android.googlesource.com/kernel/common android14-5.15-2025-10
head:   7c8286117ce253a9f730573213e63c7f74e01d69
commit: a2aa2a6c9491a807bb898220acb1062dd8226a12 [1/1] BACKPORT: KVM: Move x86's perf guest info callbacks to generic KVM
config: arm64-randconfig-1000-20260924 (https://download.01.org/0day-ci/archive/20260925/202609250707.v5In0Xad-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260925/202609250707.v5In0Xad-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/202609250707.v5In0Xad-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> arch/arm64/kvm/arm.c:493:15: warning: no previous prototype for 'kvm_arch_vcpu_get_ip' [-Wmissing-prototypes]
     493 | unsigned long kvm_arch_vcpu_get_ip(struct kvm_vcpu *vcpu)
         |               ^~~~~~~~~~~~~~~~~~~~


vim +/kvm_arch_vcpu_get_ip +493 arch/arm64/kvm/arm.c

   492	
 > 493	unsigned long kvm_arch_vcpu_get_ip(struct kvm_vcpu *vcpu)
   494	{
   495		return *vcpu_pc(vcpu);
   496	}
   497	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-09-25  0:04 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=202609250707.v5In0Xad-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.