From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kmo@daterainc.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kent Overstreet <kmo@daterainc.com>
Subject: [bcachefs:bcachefs-testing 154/174] scripts/kernel-doc: fs/bcachefs/btree_update_interior.c:1670: warning: Function parameter or struct member 'path_idx' not described in 'bch2_btree_insert_node'
Date: Mon, 18 Dec 2023 04:47:33 +0800 [thread overview]
Message-ID: <202312180414.OfsSw6NX-lkp@intel.com> (raw)
tree: https://evilpiepirate.org/git/bcachefs.git bcachefs-testing
head: 16609653d3eeb730d5a4b5d19266d52f9e7b8ea3
commit: d85fddfb75eb24146c01c54a313f57635d0c0f48 [154/174] bcachefs: Fix interior update path btree_path uses
config: i386-buildonly-randconfig-003-20231217 (https://download.01.org/0day-ci/archive/20231218/202312180414.OfsSw6NX-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231218/202312180414.OfsSw6NX-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/202312180414.OfsSw6NX-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> scripts/kernel-doc: fs/bcachefs/btree_update_interior.c:1670: warning: Function parameter or struct member 'path_idx' not described in 'bch2_btree_insert_node'
>> scripts/kernel-doc: fs/bcachefs/btree_update_interior.c:1670: warning: Excess function parameter 'path' description in 'bch2_btree_insert_node'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-17 20:47 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=202312180414.OfsSw6NX-lkp@intel.com \
--to=lkp@intel.com \
--cc=kmo@daterainc.com \
--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