From: kernel test robot <lkp@intel.com>
To: Menglong Dong <menglong8.dong@gmail.com>, mhiramat@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, rostedt@goodmis.org,
jolsa@kernel.org, mathieu.desnoyers@efficios.com,
jiang.biao@linux.dev, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing: fprobe: use ftrace if CONFIG_DYNAMIC_FTRACE_WITH_ARGS
Date: Sun, 2 Nov 2025 02:20:05 +0800 [thread overview]
Message-ID: <202511020220.bv169Bd9-lkp@intel.com> (raw)
In-Reply-To: <20251031024038.19176-1-dongml2@chinatelecom.cn>
Hi Menglong,
kernel test robot noticed the following build warnings:
[auto build test WARNING on trace/for-next]
[also build test WARNING on next-20251031]
[cannot apply to linus/master v6.18-rc3]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Menglong-Dong/tracing-fprobe-use-ftrace-if-CONFIG_DYNAMIC_FTRACE_WITH_ARGS/20251031-104301
base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link: https://lore.kernel.org/r/20251031024038.19176-1-dongml2%40chinatelecom.cn
patch subject: [PATCH v2] tracing: fprobe: use ftrace if CONFIG_DYNAMIC_FTRACE_WITH_ARGS
config: loongarch-randconfig-002-20251102 (https://download.01.org/0day-ci/archive/20251102/202511020220.bv169Bd9-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251102/202511020220.bv169Bd9-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/202511020220.bv169Bd9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/fprobe.c:340:13: warning: 'fprobe_set_ips' defined but not used [-Wunused-function]
340 | static void fprobe_set_ips(unsigned long *ips, unsigned int cnt, int remove,
| ^~~~~~~~~~~~~~
vim +/fprobe_set_ips +340 kernel/trace/fprobe.c
339
> 340 static void fprobe_set_ips(unsigned long *ips, unsigned int cnt, int remove,
341 int reset)
342 {
343 ftrace_set_filter_ips(&fprobe_graph_ops.ops, ips, cnt, remove, reset);
344 ftrace_set_filter_ips(&fprobe_ftrace_ops, ips, cnt, remove, reset);
345 }
346 #else
347 static int fprobe_ftrace_add_ips(unsigned long *addrs, int num)
348 {
349 return -ENOENT;
350 }
351
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-01 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 2:40 [PATCH v2] tracing: fprobe: use ftrace if CONFIG_DYNAMIC_FTRACE_WITH_ARGS Menglong Dong
2025-11-01 18:20 ` kernel test robot [this message]
2025-11-03 3:16 ` Masami Hiramatsu
2025-11-03 6:17 ` Menglong Dong
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=202511020220.bv169Bd9-lkp@intel.com \
--to=lkp@intel.com \
--cc=jiang.biao@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=menglong8.dong@gmail.com \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).