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:android16-6.12-sp 0/1] drivers/android/binder.c:7476:6: warning: no previous prototype for 'binder_remove_trace_events'
Date: Sat, 16 May 2026 06:35:44 +0800	[thread overview]
Message-ID: <202605160645.G6We0dGT-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 [0/1] ANDROID: binder: unload C Binder trace events
config: x86_64-randconfig-016-20260516 (https://download.01.org/0day-ci/archive/20260516/202605160645.G6We0dGT-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605160645.G6We0dGT-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/202605160645.G6We0dGT-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/android/binder.c:7476:6: warning: no previous prototype for 'binder_remove_trace_events' [-Wmissing-prototypes]
    7476 | void binder_remove_trace_events(struct module *module)
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/android/binder.c:7502:5: warning: no previous prototype for 'unload_binder' [-Wmissing-prototypes]
    7502 | int unload_binder(void)
         |     ^~~~~~~~~~~~~


vim +/binder_remove_trace_events +7476 drivers/android/binder.c

  7475	
> 7476	void binder_remove_trace_events(struct module *module)
  7477	{
  7478		struct trace_event_call *call, *tmp;
  7479		const char *name;
  7480	
  7481		mutex_lock(&event_mutex);
  7482		mutex_lock(&trace_types_lock);
  7483		down_write(&trace_event_sem);
  7484		list_for_each_entry_safe(call, tmp, &ftrace_events, list) {
  7485			name = trace_event_name(call);
  7486			if (!name || strncmp(name, "binder_", 7))
  7487				continue;
  7488			if (call->module != module)
  7489				continue;
  7490			remove_event_from_tracers(call);
  7491			list_del_init(&call->list);
  7492		}
  7493		up_write(&trace_event_sem);
  7494		mutex_unlock(&trace_types_lock);
  7495		mutex_unlock(&event_mutex);
  7496	}
  7497	EXPORT_SYMBOL_GPL(binder_remove_trace_events);
  7498	

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

                 reply	other threads:[~2026-05-15 22:35 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=202605160645.G6We0dGT-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.