From: kernel test robot <lkp@intel.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jolsa-perf:bpf/single_direct_ops 6/9] Warning: kernel/trace/ftrace.c:5980 function parameter 'ip' not described in 'register_ftrace_direct'
Date: Thu, 25 Sep 2025 14:37:04 +0200 [thread overview]
Message-ID: <202509251447.sNajLY9D-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git bpf/single_direct_ops
head: 512bde773529ffbb0241c282793b7f4641034fe7
commit: ffab58e25f3e8b2c881c0d6ead562ea1cd16ad86 [6/9] ftrace: Use direct hash interface in direct functions
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20250925/202509251447.sNajLY9D-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250925/202509251447.sNajLY9D-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/202509251447.sNajLY9D-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: kernel/trace/ftrace.c:5980 function parameter 'ip' not described in 'register_ftrace_direct'
>> Warning: kernel/trace/ftrace.c:6011 function parameter 'ip' not described in 'unregister_ftrace_direct'
>> Warning: kernel/trace/ftrace.c:6043 function parameter 'ip' not described in 'modify_ftrace_direct'
>> Warning: kernel/trace/ftrace.c:6043 function parameter 'lock_direct_mutex' not described in 'modify_ftrace_direct'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-25 12:37 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=202509251447.sNajLY9D-lkp@intel.com \
--to=lkp@intel.com \
--cc=jolsa@kernel.org \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox