From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 2/2] cifs: Implement cache I/O by accessing the cache directly
Date: Tue, 25 Jan 2022 06:24:52 +0800 [thread overview]
Message-ID: <202201250615.0L5TzebQ-lkp@intel.com> (raw)
In-Reply-To: <164304351677.2349137.11658590526534563187.stgit@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2929 bytes --]
Hi David,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on cifs/for-next]
[also build test WARNING on linus/master v5.17-rc1 next-20220124]
[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]
url: https://github.com/0day-ci/linux/commits/David-Howells/cifs-Transition-from-readpages-to-readahead/20220125-010247
base: git://git.samba.org/sfrench/cifs-2.6.git for-next
config: mips-maltasmvp_eva_defconfig (https://download.01.org/0day-ci/archive/20220125/202201250615.0L5TzebQ-lkp(a)intel.com/config)
compiler: mipsel-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/0day-ci/linux/commit/ad0df70284e96423c577eb30a366eb814888379b
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review David-Howells/cifs-Transition-from-readpages-to-readahead/20220125-010247
git checkout ad0df70284e96423c577eb30a366eb814888379b
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=mips SHELL=/bin/bash fs/
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 >>):
In file included from fs/cifs/cifsfs.c:41:
fs/cifs/fscache.h: In function 'cifs_fscache_query_occupancy':
>> fs/cifs/fscache.h:143:21: warning: assignment to 'long unsigned int *' from 'long unsigned int' makes pointer from integer without a cast [-Wint-conversion]
143 | _data_first = ULONG_MAX;
| ^
fs/cifs/fscache.h:140:57: warning: parameter '_data_first' set but not used [-Wunused-but-set-parameter]
140 | pgoff_t *_data_first,
fs/cifs/fscache.h:141:62: warning: parameter '_data_nr_pages' set but not used [-Wunused-but-set-parameter]
141 | unsigned int *_data_nr_pages)
| ~~~~~~~~~~~~~~^~~~~~~~~~~~~~
vim +143 fs/cifs/fscache.h
137
138 static inline int cifs_fscache_query_occupancy(struct inode *inode,
139 pgoff_t first, unsigned nr_pages,
140 pgoff_t *_data_first,
141 unsigned int *_data_nr_pages)
142 {
> 143 _data_first = ULONG_MAX;
144 _data_nr_pages = 0;
145 return -ENOBUFS;
146 }
147
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2022-01-24 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 16:58 [RFC PATCH 1/2] cifs: Transition from ->readpages() to ->readahead() David Howells
2022-01-24 16:58 ` [RFC PATCH 2/2] cifs: Implement cache I/O by accessing the cache directly David Howells
2022-01-24 22:24 ` kernel test robot
2022-01-24 22:24 ` kernel test robot [this message]
2022-01-25 0:26 ` 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=202201250615.0L5TzebQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.