From: kernel test robot <lkp@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
" Łukasz Bartosik" <ukaszb@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:dyndbg-bonsai-clean 63/67] kernel/trace/trace_fprobe.c:1002:13: warning: '__find_tracepoint_cb' defined but not used
Date: Wed, 23 Sep 2026 13:31:04 +0200 [thread overview]
Message-ID: <202609231335.ieFFNeIA-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git dyndbg-bonsai-clean
head: 1b386f2c853c6e84025fa93d485e69ba8c1d76f4
commit: 2d32fc9005222d1458283246043d8f704eb28f74 [63/67] kernel/tracepoint: Accelerate kernel tracepoint lookups with Bonsai Tree
config: s390-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260923/202609231335.ieFFNeIA-lkp@intel.com/config)
compiler: s390x-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260923/202609231335.ieFFNeIA-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/202609231335.ieFFNeIA-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/trace_fprobe.c:1002:13: warning: '__find_tracepoint_cb' defined but not used [-Wunused-function]
1002 | static void __find_tracepoint_cb(struct tracepoint *tp, void *priv)
| ^~~~~~~~~~~~~~~~~~~~
vim +/__find_tracepoint_cb +1002 kernel/trace/trace_fprobe.c
67e9a9ee476e86 Masami Hiramatsu (Google 2024-08-18 1001)
e2d0d7b2f42dca Masami Hiramatsu (Google 2023-06-06 @1002) static void __find_tracepoint_cb(struct tracepoint *tp, void *priv)
e2d0d7b2f42dca Masami Hiramatsu (Google 2023-06-06 1003) {
e2d0d7b2f42dca Masami Hiramatsu (Google 2023-06-06 1004) struct __find_tracepoint_cb_data *data = priv;
e2d0d7b2f42dca Masami Hiramatsu (Google 2023-06-06 1005)
e2d0d7b2f42dca Masami Hiramatsu (Google 2023-06-06 1006) if (!data->tpoint && !strcmp(data->tp_name, tp->name))
e2d0d7b2f42dca Masami Hiramatsu (Google 2023-06-06 1007) data->tpoint = tp;
e2d0d7b2f42dca Masami Hiramatsu (Google 2023-06-06 1008) }
e2d0d7b2f42dca Masami Hiramatsu (Google 2023-06-06 1009)
:::::: The code at line 1002 was first introduced by commit
:::::: e2d0d7b2f42dcaf924e9c891c91c9aa22cbbebce tracing/probes: Add tracepoint support on fprobe_events
:::::: TO: Masami Hiramatsu (Google) <mhiramat@kernel.org>
:::::: CC: Masami Hiramatsu (Google) <mhiramat@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-23 11:32 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=202609231335.ieFFNeIA-lkp@intel.com \
--to=lkp@intel.com \
--cc=jim.cromie@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ukaszb@chromium.org \
/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.