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/include/asm/kvm_define_hypevents.h:17:7: warning: no previous prototype for 'hyp_event_trace_hyp_enter'
Date: Sun, 16 Aug 2026 23:15:59 +0800 [thread overview]
Message-ID: <202608162351.tLYdgVIK-lkp@intel.com> (raw)
Hi Vincent,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android15-6.6
head: 24c059d9e217f32d61570fdbd7eb66bc999657a9
commit: f6dbfc683cf5fbbd37b6fdead1b5b08912cf6570 [2/2] ANDROID: KVM: arm64: Add support for nVHE hyp events
config: arm64-randconfig-004-20260816 (https://download.01.org/0day-ci/archive/20260816/202608162351.tLYdgVIK-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/202608162351.tLYdgVIK-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/202608162351.tLYdgVIK-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/arm64/kvm/hyp_events.c:9:
>> arch/arm64/include/asm/kvm_define_hypevents.h:17:7: warning: no previous prototype for 'hyp_event_trace_hyp_enter' [-Wmissing-prototypes]
17 | void hyp_event_trace_##__name(struct ht_iterator *iter) \
| ^~~~~~~~~~~~~~~~
arch/arm64/include/asm/kvm_hypevents.h:14:1: note: in expansion of macro 'HYP_EVENT'
14 | HYP_EVENT(hyp_enter,
| ^~~~~~~~~
>> arch/arm64/include/asm/kvm_define_hypevents.h:17:7: warning: no previous prototype for 'hyp_event_trace_hyp_exit' [-Wmissing-prototypes]
17 | void hyp_event_trace_##__name(struct ht_iterator *iter) \
| ^~~~~~~~~~~~~~~~
arch/arm64/include/asm/kvm_hypevents.h:23:1: note: in expansion of macro 'HYP_EVENT'
23 | HYP_EVENT(hyp_exit,
| ^~~~~~~~~
>> arch/arm64/kvm/hyp_events.c:100:6: warning: no previous prototype for 'hyp_trace_init_event_tracefs' [-Wmissing-prototypes]
100 | void hyp_trace_init_event_tracefs(struct dentry *parent)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> arch/arm64/kvm/hyp_events.c:130:19: warning: no previous prototype for 'hyp_trace_find_event' [-Wmissing-prototypes]
130 | struct hyp_event *hyp_trace_find_event(int id)
| ^~~~~~~~~~~~~~~~~~~~
>> arch/arm64/kvm/hyp_events.c:143:5: warning: no previous prototype for 'hyp_trace_init_events' [-Wmissing-prototypes]
143 | int hyp_trace_init_events(void)
| ^~~~~~~~~~~~~~~~~~~~~
vim +/hyp_event_trace_hyp_enter +17 arch/arm64/include/asm/kvm_define_hypevents.h
14
15 #define HYP_EVENT(__name, __proto, __struct, __assign, __printk) \
16 HYP_EVENT_FORMAT(__name, __struct); \
> 17 void hyp_event_trace_##__name(struct ht_iterator *iter) \
18 { \
19 struct trace_hyp_format_##__name __maybe_unused *__entry = \
20 (struct trace_hyp_format_##__name *)iter->ent; \
21 trace_seq_puts(&iter->seq, #__name); \
22 trace_seq_putc(&iter->seq, ' '); \
23 trace_seq_printf(&iter->seq, __printk); \
24 trace_seq_putc(&iter->seq, '\n'); \
25 }
26 #define HYP_EVENT_MULTI_READ
27 #include __HYP_EVENT_FILE
28
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-16 15:16 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=202608162351.tLYdgVIK-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.