All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 3529/3529] fs/nfs/enfs/shard_route.c:273: warning: Function parameter or member '__struct_name' not described in 'DEFINE_CLEAR_LIST_FUNC'
Date: Thu, 11 Dec 2025 05:47:14 +0800	[thread overview]
Message-ID: <202512110548.FQDvrNPq-lkp@intel.com> (raw)

Hi ChenXiaoSong,

FYI, the error/warning still remains.

tree:   https://gitee.com/openeuler/kernel.git OLK-6.6
head:   d281438782e3c28a3df71a64513a3312d43dcf01
commit: 2d5981287b67cc1a5d9231bff267f90001251ba3 [3529/3529] nfs/enfs: introduce DEFINE_CLEAR_LIST_FUNC to define enfs_clear_fs_info()
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20251211/202512110548.FQDvrNPq-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251211/202512110548.FQDvrNPq-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/202512110548.FQDvrNPq-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> fs/nfs/enfs/shard_route.c:273: warning: Function parameter or member '__struct_name' not described in 'DEFINE_CLEAR_LIST_FUNC'
>> fs/nfs/enfs/shard_route.c:273: warning: Function parameter or member '__list_name' not described in 'DEFINE_CLEAR_LIST_FUNC'
   fs/nfs/enfs/shard_route.c:273: warning: expecting prototype for enfs_clear_ ## __struct_name()(). Prototype was for DEFINE_CLEAR_LIST_FUNC() instead
   fs/nfs/enfs/shard_route.c:349: warning: Cannot understand  * @return:0 for success,otherwise for failed
    on line 349 - I thought it was a doc line


vim +273 fs/nfs/enfs/shard_route.c

   256	
   257	/**
   258	 * enfs_clear_ ## __struct_name() - delete and free all __struct_name from view_table
   259	 * @table: view table
   260	 *
   261	 * Context: protected by view_table write lock
   262	 * Return: None
   263	 */
   264	#define DEFINE_CLEAR_LIST_FUNC(__struct_name, __list_name)		\
   265	static void enfs_clear_ ## __struct_name(struct view_table *table)	\
   266	{									\
   267		struct __struct_name *item, *tmp;				\
   268										\
   269		list_for_each_entry_safe(item, tmp, &table->__list_name, next) {\
   270			list_del(&item->next);					\
   271			kfree(item);						\
   272		}								\
 > 273	}
   274	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-12-10 21: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=202512110548.FQDvrNPq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel@openeuler.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 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.