From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-kiwi-6.1 166/166] fs/smb/client/cifsroot.c:83:12: warning: no previous prototype for function 'cifs_root_data'
Date: Thu, 02 Jul 2026 11:56:41 +0800 [thread overview]
Message-ID: <202607021152.CulFVz6u-lkp@intel.com> (raw)
Hi Steve,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android14-kiwi-6.1
head: 2a9e8b82544e3c1e2678c2c07bef3d3706156ee4
commit: 29429a1f5871dbe54ee0da81bb12db8567f15379 [166/166] smb: move client and server files to common directory fs/smb
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20260702/202607021152.CulFVz6u-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260702/202607021152.CulFVz6u-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/202607021152.CulFVz6u-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from <built-in>:3:
In file included from include/linux/compiler_types.h:94:
include/linux/compiler-clang.h:24:9: warning: '__SANITIZE_ADDRESS__' macro redefined [-Wmacro-redefined]
24 | #define __SANITIZE_ADDRESS__
| ^
<built-in>:353:9: note: previous definition is here
353 | #define __SANITIZE_ADDRESS__ 1
| ^
>> fs/smb/client/cifsroot.c:83:12: warning: no previous prototype for function 'cifs_root_data' [-Wmissing-prototypes]
83 | int __init cifs_root_data(char **dev, char **opts)
| ^
fs/smb/client/cifsroot.c:83:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
83 | int __init cifs_root_data(char **dev, char **opts)
| ^
| static
2 warnings generated.
vim +/cifs_root_data +83 fs/smb/client/cifsroot.c
8eecd1c2e5bc73d fs/cifs/cifsroot.c Paulo Alcantara (SUSE 2019-07-16 82)
8eecd1c2e5bc73d 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
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-02 3:57 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=202607021152.CulFVz6u-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.