From: kernel test robot <lkp@intel.com>
To: Andrea Tomassetti <andrea.tomassetti@devo.com>,
linux-bcache@vger.kernel.org
Cc: kbuild-all@lists.01.org, Coly Li <colyli@suse.de>,
Kent Overstreet <kmo@daterainc.com>,
Zhang Zhen <zhangzhen.email@gmail.com>,
Andrea Tomassetti <andrea.tomassetti@devo.com>
Subject: Re: [PATCH] bcache: Use bcache without formatting existing device
Date: Thu, 10 Mar 2022 20:09:34 +0800 [thread overview]
Message-ID: <202203102007.cDiegien-lkp@intel.com> (raw)
In-Reply-To: <20220310085240.334068-1-andrea.tomassetti@devo.com>
Hi Andrea,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.17-rc7 next-20220309]
[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/Andrea-Tomassetti/bcache-Use-bcache-without-formatting-existing-device/20220310-165353
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 3bf7edc84a9eb4007dd9a0cb8878a7e1d5ec6a3b
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220310/202203102007.cDiegien-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/b5073e4ece2a86f002ca66fb1d864034c12be3e2
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Andrea-Tomassetti/bcache-Use-bcache-without-formatting-existing-device/20220310-165353
git checkout b5073e4ece2a86f002ca66fb1d864034c12be3e2
# save the config file to linux build tree
mkdir build_dir
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/md/bcache/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/md/bcache/control.c:18:6: sparse: sparse: symbol 'bch_service_ioctl_ctrl' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2022-03-10 12:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 8:52 [PATCH] bcache: Use bcache without formatting existing device Andrea Tomassetti
2022-03-10 10:58 ` kernel test robot
2022-03-10 11:18 ` kernel test robot
2022-03-10 12:07 ` [RFC PATCH] bcache: bch_service_ioctl_ctrl() can be static kernel test robot
2022-03-10 12:09 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-04 15:13 [PATCH] bcache: Use bcache without formatting existing device Andrea Tomassetti
2022-07-04 15:29 ` Coly Li
2022-07-05 8:48 ` Andrea Tomassetti
2022-07-05 14:04 ` Coly Li
2022-07-05 22:03 ` Eric Wheeler
2022-07-07 9:56 ` Andrea Tomassetti
2022-07-12 20:29 ` Eric Wheeler
2022-07-20 8:06 ` Andrea Tomassetti
2022-07-20 13:31 ` Coly Li
2022-07-20 14:23 ` Andrea Tomassetti
2022-07-20 14:46 ` Coly Li
2022-03-08 14:56 Andrea Tomassetti
2022-03-09 1:41 ` Zhang Zhen
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=202203102007.cDiegien-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrea.tomassetti@devo.com \
--cc=colyli@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=zhangzhen.email@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 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).