From: Steve French <smfrench@gmail.com>
To: kernel test robot <lkp@intel.com>, Paulo Alcantara <pc@cjr.nz>
Cc: kbuild-all@lists.01.org, CIFS <linux-cifs@vger.kernel.org>,
samba-technical <samba-technical@lists.samba.org>
Subject: Re: [cifs:for-next 1/1] fs/smbfs/cifsroot.c:83:12: warning: no previous prototype for 'cifs_root_data'
Date: Mon, 13 Sep 2021 23:14:37 -0500 [thread overview]
Message-ID: <CAH2r5msMZFtQt-u+5bw=hXTe4J_s8ugb2JR9RLCP4+9J3Pkzmg@mail.gmail.com> (raw)
In-Reply-To: <202109132243.2u0FFC0r-lkp@intel.com>
Paulo,
This doesn't look like an error - there is a prototype for this in
init/do_mount.c
Is a change needed? Or something to quiet the buildbot ..
On Mon, Sep 13, 2021 at 10:00 AM kernel test robot <lkp@intel.com> wrote:
>
> tree: git://git.samba.org/sfrench/cifs-2.6.git for-next
> head: bba805a46c91e7a8a1d04704e5409f890acf8b66
> commit: bba805a46c91e7a8a1d04704e5409f890acf8b66 [1/1] cifs: rename fs/cifs directory to fs/smbfs
> config: x86_64-allyesconfig (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> git remote add cifs git://git.samba.org/sfrench/cifs-2.6.git
> git fetch --no-tags cifs for-next
> git checkout bba805a46c91e7a8a1d04704e5409f890acf8b66
> # save the attached .config to linux build tree
> make W=1 ARCH=x86_64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> >> fs/smbfs/cifsroot.c:83:12: warning: no previous prototype for 'cifs_root_data' [-Wmissing-prototypes]
> 83 | int __init cifs_root_data(char **dev, char **opts)
> | ^~~~~~~~~~~~~~
>
>
> vim +/cifs_root_data +83 fs/smbfs/cifsroot.c
>
> 8eecd1c2e5bc73 fs/cifs/cifsroot.c Paulo Alcantara (SUSE 2019-07-16 82)
> 8eecd1c2e5bc73 fs/cifs/cifsroot.c Paulo Alcantara (SUSE 2019-07-16 @83) int __init cifs_root_data(char **dev, char **opts)
>
> :::::: The code at line 83 was first introduced by commit
> :::::: 8eecd1c2e5bc73d33f3a544751305679dbf88eb4 cifs: Add support for root file systems
>
> :::::: TO: Paulo Alcantara (SUSE) <paulo@paulo.ac>
> :::::: CC: Steve French <stfrench@microsoft.com>
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
--
Thanks,
Steve
prev parent reply other threads:[~2021-09-14 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 14:49 [cifs:for-next 1/1] fs/smbfs/cifsroot.c:83:12: warning: no previous prototype for 'cifs_root_data' kernel test robot
2021-09-14 4:14 ` Steve French [this message]
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='CAH2r5msMZFtQt-u+5bw=hXTe4J_s8ugb2JR9RLCP4+9J3Pkzmg@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-cifs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pc@cjr.nz \
--cc=samba-technical@lists.samba.org \
/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;
as well as URLs for NNTP newsgroup(s).