From: kernel test robot <lkp@intel.com>
To: Steve French <stfrench@microsoft.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Ronnie Sahlberg <lsahlber@redhat.com>
Subject: [asahilinux:tipd/v2 1497/2972] fs/smbfs_client/cifsroot.c:83:12: error: no previous prototype for 'cifs_root_data'
Date: Tue, 9 Nov 2021 09:19:48 +0800 [thread overview]
Message-ID: <202111090939.2nPOVfSh-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
Hi Steve,
First bad commit (maybe != root cause):
tree: https://github.com/AsahiLinux/linux tipd/v2
head: 33646424fbe83c154fa7bfee199e261631e445ed
commit: b4a8c8f8fa8b7b86bb62257fbb27e7bde58ac97e [1497/2972] cifs: rename fs/cifs directory to fs/smbfs_client
config: nios2-allyesconfig (attached as .config)
compiler: nios2-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/AsahiLinux/linux/commit/b4a8c8f8fa8b7b86bb62257fbb27e7bde58ac97e
git remote add asahilinux https://github.com/AsahiLinux/linux
git fetch --no-tags asahilinux tipd/v2
git checkout b4a8c8f8fa8b7b86bb62257fbb27e7bde58ac97e
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=nios2
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/smbfs_client/cifsroot.c:83:12: error: no previous prototype for 'cifs_root_data' [-Werror=missing-prototypes]
83 | int __init cifs_root_data(char **dev, char **opts)
| ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/cifs_root_data +83 fs/smbfs_client/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
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 60771 bytes --]
next reply other threads:[~2021-11-09 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 1:19 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-01 16:04 [asahilinux:tipd/v2 1497/2972] fs/smbfs_client/cifsroot.c:83:12: error: no previous prototype for 'cifs_root_data' kernel test robot
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=202111090939.2nPOVfSh-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=stfrench@microsoft.com \
/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).