From: kernel test robot <lkp@intel.com>
To: Kundan Kumar <kundan.kumar@samsung.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Luis Chamberlain <mcgrof@kernel.org>,
Anuj Gupta <anuj20.g@samsung.com>
Subject: [mcgrof:20250807-migrate-folios-stats-pw 2/16] Warning: fs/fs-writeback.c:1008 function parameter 'bdi_wb_ctx' not described in 'bdi_split_work_to_wbs'
Date: Thu, 7 Aug 2025 23:40:13 +0200 [thread overview]
Message-ID: <202508072355.WudSLBwt-lkp@intel.com> (raw)
Hi Kundan,
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/mcgrof/linux.git 20250807-migrate-folios-stats-pw
head: 9e85a0c893452d1be01703635526b5ce793760f3
commit: bff8f032a029ab66ff54c19048c9f45489da6a8e [2/16] writeback: add infra for parallel writeback
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250807/202508072355.WudSLBwt-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250807/202508072355.WudSLBwt-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/202508072355.WudSLBwt-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/fs-writeback.c:1008 function parameter 'bdi_wb_ctx' not described in 'bdi_split_work_to_wbs'
--
>> Warning: mm/backing-dev.c:788 function parameter 'bdi_wb_ctx' not described in 'wb_get_lookup'
>> Warning: mm/backing-dev.c:788 Excess function parameter 'bdi' description in 'wb_get_lookup'
>> Warning: mm/backing-dev.c:823 function parameter 'bdi_wb_ctx' not described in 'wb_get_create'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-07 21:40 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=202508072355.WudSLBwt-lkp@intel.com \
--to=lkp@intel.com \
--cc=anuj20.g@samsung.com \
--cc=kundan.kumar@samsung.com \
--cc=llvm@lists.linux.dev \
--cc=mcgrof@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 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).