From: kernel test robot <lkp@intel.com>
To: mingzhe <mingzhe.zou@easystack.cn>,
colyli@suse.de, bcache@lists.ewheeler.net,
andrea.tomassetti-opensource@devo.com
Cc: oe-kbuild-all@lists.linux.dev, linux-bcache@vger.kernel.org,
zoumingzhe@qq.com
Subject: Re: [PATCH v6 1/3] bcache: add dirty_data in struct bcache_device
Date: Tue, 7 Mar 2023 20:02:41 +0800 [thread overview]
Message-ID: <202303071948.FdodHBjj-lkp@intel.com> (raw)
In-Reply-To: <20230307101842.2450-1-mingzhe.zou@easystack.cn>
Hi mingzhe,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.3-rc1 next-20230307]
[cannot apply to song-md/md-next device-mapper-dm/for-next]
[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/mingzhe/bcache-allocate-stripe-memory-when-partial_stripes_expensive-is-true/20230307-181923
patch link: https://lore.kernel.org/r/20230307101842.2450-1-mingzhe.zou%40easystack.cn
patch subject: [PATCH v6 1/3] bcache: add dirty_data in struct bcache_device
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 12.1.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/intel-lab-lkp/linux/commit/9c7354d0ffcbc41178540901315f22fb0a16b11a
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review mingzhe/bcache-allocate-stripe-memory-when-partial_stripes_expensive-is-true/20230307-181923
git checkout 9c7354d0ffcbc41178540901315f22fb0a16b11a
# save the config file
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 ARCH=m68k olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 ARCH=m68k
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303071948.FdodHBjj-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/Kconfig:42: can't open file "drivers/md/Kconfig"
make[2]: *** [scripts/kconfig/Makefile:77: allyesconfig] Error 1
make[1]: *** [Makefile:693: allyesconfig] Error 2
make: *** [Makefile:226: __sub-make] Error 2
make: Target 'allyesconfig' not remade because of errors.
--
>> drivers/Kconfig:42: can't open file "drivers/md/Kconfig"
make[2]: *** [scripts/kconfig/Makefile:77: oldconfig] Error 1
make[1]: *** [Makefile:693: oldconfig] Error 2
make: *** [Makefile:226: __sub-make] Error 2
make: Target 'oldconfig' not remade because of errors.
--
>> drivers/Kconfig:42: can't open file "drivers/md/Kconfig"
make[2]: *** [scripts/kconfig/Makefile:77: olddefconfig] Error 1
make[1]: *** [Makefile:693: olddefconfig] Error 2
make: *** [Makefile:226: __sub-make] Error 2
make: Target 'olddefconfig' not remade because of errors.
vim +42 drivers/Kconfig
c6fd280766a050 Jeff Garzik 2006-08-10 41
^1da177e4c3f41 Linus Torvalds 2005-04-16 @42 source "drivers/md/Kconfig"
^1da177e4c3f41 Linus Torvalds 2005-04-16 43
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
prev parent reply other threads:[~2023-03-07 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 10:18 [PATCH v6 1/3] bcache: add dirty_data in struct bcache_device mingzhe
2023-03-07 10:18 ` [PATCH v6 2/3] bcache: allocate stripe memory when partial_stripes_expensive is true mingzhe
2023-03-07 10:18 ` [PATCH v6 3/3] bcache: support online resizing of cached_dev mingzhe
2023-03-07 12:02 ` kernel test robot [this message]
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=202303071948.FdodHBjj-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrea.tomassetti-opensource@devo.com \
--cc=bcache@lists.ewheeler.net \
--cc=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=mingzhe.zou@easystack.cn \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zoumingzhe@qq.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 read-only IMAP folder(s) and NNTP newsgroup(s).