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-sp 1/1] kernel/trace/trace_events.c:2807:6: warning: no previous prototype for 'remove_event_from_tracers'
Date: Sat, 16 May 2026 06:23:22 +0800 [thread overview]
Message-ID: <202605160607.pSTEcSVp-lkp@intel.com> (raw)
Hi Alice,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12-sp
head: f815f5cffc922b8894200a0522dcb04211c469ec
commit: 43c26111cafa87d81570c63d96c497e13ec883da [1/1] ANDROID: binder: unload C Binder trace events
config: arm64-randconfig-003-20260516 (https://download.01.org/0day-ci/archive/20260516/202605160607.pSTEcSVp-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605160607.pSTEcSVp-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/202605160607.pSTEcSVp-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/trace_events.c:2807:6: warning: no previous prototype for 'remove_event_from_tracers' [-Wmissing-prototypes]
2807 | void remove_event_from_tracers(struct trace_event_call *call)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/remove_event_from_tracers +2807 kernel/trace/trace_events.c
2806
> 2807 void remove_event_from_tracers(struct trace_event_call *call)
2808 {
2809 struct trace_event_file *file;
2810 struct trace_array *tr;
2811
2812 do_for_each_event_file_safe(tr, file) {
2813 if (file->event_call != call)
2814 continue;
2815
2816 remove_event_file_dir(file);
2817 /*
2818 * The do_for_each_event_file_safe() is
2819 * a double loop. After finding the call for this
2820 * trace_array, we use break to jump to the next
2821 * trace_array.
2822 */
2823 break;
2824 } while_for_each_event_file();
2825 }
2826
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-15 22:23 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=202605160607.pSTEcSVp-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.