From: kernel test robot <lkp@intel.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jolsa-perf:bpf/tracing_multi_6 4/24] kernel/bpf/trampoline.c:767:12: warning: 'bpf_trampoline_update' defined but not used
Date: Fri, 06 Mar 2026 10:58:18 +0800 [thread overview]
Message-ID: <202603061049.APFgL04A-lkp@intel.com> (raw)
Hi Jiri,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git bpf/tracing_multi_6
head: af446b2f2e0f478bc501b1791673d2aa5994101b
commit: ae934a5d41127a973581eb684721b967d5cf8a0c [4/24] bpf: Add struct bpf_trampoline_ops object
config: sparc64-randconfig-001-20260306 (https://download.01.org/0day-ci/archive/20260306/202603061049.APFgL04A-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 14.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260306/202603061049.APFgL04A-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/202603061049.APFgL04A-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/bpf/trampoline.c:767:12: warning: 'bpf_trampoline_update' defined but not used [-Wunused-function]
767 | static int bpf_trampoline_update(struct bpf_trampoline *tr, bool lock_direct_mutex)
| ^~~~~~~~~~~~~~~~~~~~~
vim +/bpf_trampoline_update +767 kernel/bpf/trampoline.c
766
> 767 static int bpf_trampoline_update(struct bpf_trampoline *tr, bool lock_direct_mutex)
768 {
769 return bpf_trampoline_update_ops(tr, lock_direct_mutex, &trampoline_ops, NULL);
770 }
771
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-06 2:58 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=202603061049.APFgL04A-lkp@intel.com \
--to=lkp@intel.com \
--cc=jolsa@kernel.org \
--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.