All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [intel-lts:6.6/preempt-rt 3/3] fs/hostfs/hostfs_kern.c:972:9: error: implicit declaration of function 'fsparam_string_empty'; did you mean 'fsparam_string'?
Date: Sun, 16 Feb 2025 12:36:11 +0800	[thread overview]
Message-ID: <202502161242.HGh7Uabf-lkp@intel.com> (raw)

tree:   https://github.com/intel/linux-intel-lts.git 6.6/preempt-rt
head:   da3aec3fdaa3fcb8c9f9760d4edef06741ccfc6e
commit: be80de30b347dc2eae35dd5f7905ad9c9167dc08 [3/3] hostfs: fix the host directory parse when mounting.
config: um-allyesconfig (https://download.01.org/0day-ci/archive/20250216/202502161242.HGh7Uabf-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250216/202502161242.HGh7Uabf-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/202502161242.HGh7Uabf-lkp@intel.com/

All errors (new ones prefixed by >>):

>> fs/hostfs/hostfs_kern.c:972:9: error: implicit declaration of function 'fsparam_string_empty'; did you mean 'fsparam_string'? [-Werror=implicit-function-declaration]
     972 |         fsparam_string_empty("hostfs",          Opt_hostfs),
         |         ^~~~~~~~~~~~~~~~~~~~
         |         fsparam_string
   fs/hostfs/hostfs_kern.c:972:9: warning: initialization of 'const char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
   fs/hostfs/hostfs_kern.c:972:9: note: (near initialization for 'hostfs_param_specs[0].name')
>> fs/hostfs/hostfs_kern.c:972:9: error: initializer element is not constant
   fs/hostfs/hostfs_kern.c:972:9: note: (near initialization for 'hostfs_param_specs[0].name')
   fs/hostfs/hostfs_kern.c:973:9: warning: braces around scalar initializer
     973 |         {}
         |         ^
   fs/hostfs/hostfs_kern.c:973:9: note: (near initialization for 'hostfs_param_specs[0].type')
   cc1: some warnings being treated as errors


vim +972 fs/hostfs/hostfs_kern.c

   970	
   971	static const struct fs_parameter_spec hostfs_param_specs[] = {
 > 972		fsparam_string_empty("hostfs",		Opt_hostfs),
   973		{}
   974	};
   975	

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

                 reply	other threads:[~2025-02-16  4:36 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=202502161242.HGh7Uabf-lkp@intel.com \
    --to=lkp@intel.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.