From: kernel test robot <lkp@intel.com>
To: Enzo Matsumiya <ematsumiya@suse.de>, linux-cifs@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
smfrench@gmail.com, pc@cjr.nz, ronniesahlberg@gmail.com,
nspmangalore@gmail.com
Subject: Re: [PATCH] cifs: split procfs from debug code
Date: Mon, 25 Jul 2022 02:01:49 +0800 [thread overview]
Message-ID: <202207250111.xRaRSq5I-lkp@intel.com> (raw)
In-Reply-To: <20220724145735.5853-1-ematsumiya@suse.de>
Hi Enzo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on cifs/for-next]
[also build test ERROR on next-20220722]
[cannot apply to linus/master v5.19-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Enzo-Matsumiya/cifs-split-procfs-from-debug-code/20220724-225846
base: git://git.samba.org/sfrench/cifs-2.6.git for-next
config: i386-randconfig-a006 (https://download.01.org/0day-ci/archive/20220725/202207250111.xRaRSq5I-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 12fbd2d377e396ad61bce56d71c98a1eb1bebfa9)
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/intel-lab-lkp/linux/commit/a9bbb62b87033fb57943ff221160dbf92e84e297
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Enzo-Matsumiya/cifs-split-procfs-from-debug-code/20220724-225846
git checkout a9bbb62b87033fb57943ff221160dbf92e84e297
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "cifs_dump_mem" [fs/cifs/cifs.ko] undefined!
>> ERROR: modpost: "cifs_dump_detail" [fs/cifs/cifs.ko] undefined!
--
In file included from fs/cifs/cifssmb.c:31:
>> fs/cifs/debug.h:14:20: warning: function 'cifs_dump_mem' has internal linkage but is not defined [-Wundefined-internal]
static inline void cifs_dump_mem(char *label, void *data, int length);
^
fs/cifs/cifssmb.c:418:2: note: used here
cifs_dump_mem("Invalid transact2 SMB: ", (char *)pSMB,
^
1 warning generated.
--
In file included from fs/cifs/smb1ops.c:13:
>> fs/cifs/debug.h:15:20: warning: function 'cifs_dump_detail' has internal linkage but is not defined [-Wundefined-internal]
static inline void cifs_dump_detail(void *buf, struct TCP_Server_Info *ptcp_info);
^
fs/cifs/smb1ops.c:1172:17: note: used here
.dump_detail = cifs_dump_detail,
^
1 warning generated.
--
fs/cifs/connect.c:2739:24: warning: variable 'saddr4' set but not used [-Wunused-but-set-variable]
struct sockaddr_in *saddr4;
^
In file included from fs/cifs/connect.c:39:
>> fs/cifs/debug.h:14:20: warning: function 'cifs_dump_mem' has internal linkage but is not defined [-Wundefined-internal]
static inline void cifs_dump_mem(char *label, void *data, int length);
^
fs/cifs/connect.c:1054:3: note: used here
cifs_dump_mem("Bad SMB: ", buf,
^
2 warnings generated.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-07-24 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 14:57 [PATCH] cifs: split procfs from debug code Enzo Matsumiya
2022-07-24 18:01 ` kernel test robot [this message]
2022-07-24 19:54 ` 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=202207250111.xRaRSq5I-lkp@intel.com \
--to=lkp@intel.com \
--cc=ematsumiya@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-cifs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nspmangalore@gmail.com \
--cc=pc@cjr.nz \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.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 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.