From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6 2/2] arch/arm64/kvm/hyp/nvhe/trace.c:174:15: warning: no previous prototype for 'rb_event_size'
Date: Sun, 16 Aug 2026 18:40:23 +0800 [thread overview]
Message-ID: <202608161839.5EVXqib7-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android15-6.6
head: 24c059d9e217f32d61570fdbd7eb66bc999657a9
commit: 794f874404060e7e14863872950b53e6a7aa9b68 [2/2] ANDROID: KVM: arm64: Add tracing support for the nVHE hyp
config: arm64-randconfig-004-20260816 (https://download.01.org/0day-ci/archive/20260816/202608161839.5EVXqib7-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260816/202608161839.5EVXqib7-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/202608161839.5EVXqib7-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/arm64/kvm/hyp/nvhe/trace.c: In function 'rb_move_tail':
arch/arm64/kvm/hyp/nvhe/trace.c:134:49: warning: variable 'new_head' set but not used [-Wunused-but-set-variable]
134 | struct hyp_buffer_page *tail_page, *new_tail, *new_head;
| ^~~~~~~~
arch/arm64/kvm/hyp/nvhe/trace.c: At top level:
>> arch/arm64/kvm/hyp/nvhe/trace.c:174:15: warning: no previous prototype for 'rb_event_size' [-Wmissing-prototypes]
174 | unsigned long rb_event_size(unsigned long length)
| ^~~~~~~~~~~~~
vim +/rb_event_size +174 arch/arm64/kvm/hyp/nvhe/trace.c
173
> 174 unsigned long rb_event_size(unsigned long length)
175 {
176 struct ring_buffer_event *event;
177
178 return length + RB_EVNT_HDR_SIZE + sizeof(event->array[0]);
179 }
180
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-16 10:40 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=202608161839.5EVXqib7-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.