From: kernel test robot <lkp@intel.com>
To: Cai Xinchen <caixinchen1@huawei.com>,
mic@digikod.net, gnoack@google.com, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com, corbet@lwn.net,
skhan@linuxfoundation.org, utilityemal77@gmail.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, ihor.solodrai@linux.dev,
rdunlap@infradead.org, gregkh@linuxfoundation.org,
rafael@kernel.org, dakr@kernel.org, johan@kernel.org,
dlemoal@kernel.org, hch@lst.de, axboe@kernel.dk,
viro@zeniv.linux.org.uk, brauner@kernel.org
Subject: Re: [PATCH v3 -next 01/18] fs: pass struct path to notify_change()
Date: Mon, 2 Nov 2026 01:23:18 +0800 [thread overview]
Message-ID: <202611020100.FxxaH8E9-lkp@intel.com> (raw)
In-Reply-To: <20261027121151.1887650-2-caixinchen1@huawei.com>
Hi Cai,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20261026]
url: https://github.com/intel-lab-lkp/linux/commits/Cai-Xinchen/fs-pass-struct-path-to-notify_change/20261027-201134
base: next-20261026
patch link: https://lore.kernel.org/r/20261027121151.1887650-2-caixinchen1%40huawei.com
patch subject: [PATCH v3 -next 01/18] fs: pass struct path to notify_change()
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20261102/202611020100.FxxaH8E9-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project c2ea4440d4b64c148de4fdfca1fc2c437a0701e4)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261102/202611020100.FxxaH8E9-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/202611020100.FxxaH8E9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/nfsd/nfs4state.c:10537 function parameter 'path' not described in 'nfsd4_deleg_getattr_conflict'
>> Warning: fs/nfsd/nfs4state.c:10537 Excess function parameter 'dentry' description in 'nfsd4_deleg_getattr_conflict'
>> Warning: fs/nfsd/nfs4state.c:10537 function parameter 'path' not described in 'nfsd4_deleg_getattr_conflict'
>> Warning: fs/nfsd/nfs4state.c:10537 Excess function parameter 'dentry' description in 'nfsd4_deleg_getattr_conflict'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-11-01 17:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20261027121151.1887650-2-caixinchen1@huawei.com>]
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=202611020100.FxxaH8E9-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=caixinchen1@huawei.com \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dlemoal@kernel.org \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=gnoack@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=ihor.solodrai@linux.dev \
--cc=jmorris@namei.org \
--cc=johan@kernel.org \
--cc=jolsa@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mic@digikod.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=serge@hallyn.com \
--cc=skhan@linuxfoundation.org \
--cc=song@kernel.org \
--cc=utilityemal77@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yonghong.song@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