[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201712201731.MFNolYyj%fengguang.wu@intel.com>
Date: Wed, 20 Dec 2017 18:01:21 +0800
From: kbuild test robot <lkp@...el.com>
To: Scott Bauer <scott.bauer@...el.com>
Cc: kbuild-all@...org, dm-devel@...hat.com, snitzer@...hat.com,
agk@...hat.com, linux-kernel@...r.kernel.org,
keith.busch@...el.com, jonathan.derrick@...el.com,
Scott Bauer <scott.bauer@...el.com>
Subject: Re: [PATCH v4 1/2] dm-unstripe: unstripe RAID 0/dm-striped device
Hi Scott,
I love your patch! Yet something to improve:
[auto build test ERROR on dm/for-next]
[also build test ERROR on v4.15-rc4]
[cannot apply to next-20171220]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Scott-Bauer/dm-unstripe/20171220-121845
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=m68k
All errors (new ones prefixed by >>):
drivers/md/dm-unstripe.o: In function `set_ctr':
>> dm-unstripe.c:(.text+0x36a): undefined reference to `__udivdi3'
>> dm-unstripe.c:(.text+0x384): undefined reference to `__umoddi3'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Download attachment ".config.gz" of type "application/gzip" (45398 bytes)
Powered by blists - more mailing lists