From: kernel test robot <lkp@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dgc-xfs:vfs-scale 1/11] lib/dlock-list.c:198: warning: Excess function parameter 'dlist' description in '__dlock_list_next_list'
Date: Wed, 6 Dec 2023 21:03:20 +0800 [thread overview]
Message-ID: <202312062040.baSag4OL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git vfs-scale
head: 5e5e95a86ea3aa15d83654ec3752451959a689e6
commit: e110421085e9f39f401af6f6cbf40816751f18b2 [1/11] lib/dlock-list: Distributed and lock-protected lists
config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20231206/202312062040.baSag4OL-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231206/202312062040.baSag4OL-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/202312062040.baSag4OL-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> lib/dlock-list.c:198: warning: Excess function parameter 'dlist' description in '__dlock_list_next_list'
vim +198 lib/dlock-list.c
188
189 /**
190 * __dlock_list_next_list: Find the first entry of the next available list
191 * @dlist: Pointer to the dlock_list_heads structure
192 * @iter : Pointer to the dlock list iterator structure
193 * Return: true if the entry is found, false if all the lists exhausted
194 *
195 * The information about the next available list will be put into the iterator.
196 */
197 struct dlock_list_node *__dlock_list_next_list(struct dlock_list_iter *iter)
> 198 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-06 13:03 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=202312062040.baSag4OL-lkp@intel.com \
--to=lkp@intel.com \
--cc=david@fromorbit.com \
--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.