From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Chuck Lever <chuck.lever@oracle.com>
Subject: [cel:nfsd-testing 14/56] Warning: fs/nfsd/export.c:579 Cannot find identifier on line:
Date: Mon, 04 May 2026 02:10:27 +0800 [thread overview]
Message-ID: <202605040126.wqshRbp4-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux nfsd-testing
head: 22ca5f8e836e43f49c9b622f60e7ee48012a81c3
commit: e294087f9d1b3fe2cf7d8522bdc58d9d0662cf7e [14/56] nfsd: add netlink upcall for the svc_export cache
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260504/202605040126.wqshRbp4-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260504/202605040126.wqshRbp4-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/202605040126.wqshRbp4-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/nfsd/export.c:579 Cannot find identifier on line:
* @cd: cache_detail for the svc_export cache
Warning: fs/nfsd/export.c:580 Cannot find identifier on line:
* @attr: nested attribute containing svc-export fields
Warning: fs/nfsd/export.c:581 Cannot find identifier on line:
*
>> Warning: fs/nfsd/export.c:582 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* Parses one svc-export entry from a netlink message and updates the
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-03 18:11 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=202605040126.wqshRbp4-lkp@intel.com \
--to=lkp@intel.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@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 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.