From: kernel test robot <lkp@intel.com>
To: Wen Yang <wen.yang@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: Warning: kernel/trace/rv/rv_uprobe.c:17 function parameter 'binpath' not described in 'rv_uprobe_register'
Date: Mon, 31 Aug 2026 05:20:38 +0200 [thread overview]
Message-ID: <202608310514.CurHoWr4-lkp@intel.com> (raw)
Hi Wen,
First bad commit (maybe != root cause):
tree: https://github.com/intel-lab-lkp/linux/commits/wen-yang-linux-dev/rv-Introduce-DA_MON_ALLOCATION_STRATEGY/20260821-004510
head: ea162b44eca3c65889cd39be8bbdc29084f58e43
commit: 8161ebbed0a8c3da681d32a7234399a1c814c2d5 rv: Add tlob hybrid automaton monitor
date: 10 days ago
config: mips-allyesconfig (https://download.01.org/0day-ci/archive/20260831/202608310514.CurHoWr4-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260831/202608310514.CurHoWr4-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/202608310514.CurHoWr4-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: kernel/trace/rv/rv_uprobe.c:17 function parameter 'binpath' not described in 'rv_uprobe_register'
>> Warning: kernel/trace/rv/rv_uprobe.c:17 function parameter 'offset' not described in 'rv_uprobe_register'
>> Warning: kernel/trace/rv/rv_uprobe.c:17 function parameter 'p' not described in 'rv_uprobe_register'
>> Warning: kernel/trace/rv/rv_uprobe.c:49 function parameter 'p' not described in 'rv_uprobe_is_registered'
>> Warning: kernel/trace/rv/rv_uprobe.c:58 function parameter 'p' not described in 'rv_uprobe_unregister'
>> Warning: kernel/trace/rv/rv_uprobe.c:73 function parameter 'p' not described in 'rv_uprobe_unregister_nosync'
>> Warning: kernel/trace/rv/rv_uprobe.c:17 function parameter 'binpath' not described in 'rv_uprobe_register'
>> Warning: kernel/trace/rv/rv_uprobe.c:17 function parameter 'offset' not described in 'rv_uprobe_register'
>> Warning: kernel/trace/rv/rv_uprobe.c:17 function parameter 'p' not described in 'rv_uprobe_register'
>> Warning: kernel/trace/rv/rv_uprobe.c:49 function parameter 'p' not described in 'rv_uprobe_is_registered'
>> Warning: kernel/trace/rv/rv_uprobe.c:58 function parameter 'p' not described in 'rv_uprobe_unregister'
>> Warning: kernel/trace/rv/rv_uprobe.c:73 function parameter 'p' not described in 'rv_uprobe_unregister_nosync'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-31 3:21 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=202608310514.CurHoWr4-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wen.yang@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.