From: kbuild test robot <fengguang.wu@intel.com>
To: Mike Christie <mchristi@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>
Subject: ERROR: "__ucmpdi2" [drivers/scsi/sd_mod.ko] undefined!
Date: Sun, 14 Aug 2016 20:39:06 +0800 [thread overview]
Message-ID: <201608142002.0xj2aheW%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Hi Mike,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 118253a593bd1c57de2d1193df1ccffe1abe745b
commit: 4e1b2d52a80d79296a5d899d73249748dea71a53 block, fs, drivers: remove REQ_OP compat defs and related code
date: 10 weeks ago
config: blackfin-CM-BF548_defconfig (attached as .config)
compiler: bfin-uclinux-gcc (GCC) 4.6.3
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 4e1b2d52a80d79296a5d899d73249748dea71a53
# save the attached .config to linux build tree
make.cross ARCH=blackfin
All errors (new ones prefixed by >>):
>> ERROR: "__ucmpdi2" [drivers/scsi/sd_mod.ko] undefined!
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 14139 bytes --]
next reply other threads:[~2016-08-14 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 12:39 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-11 21:46 kbuild test robot
2016-09-04 17:12 kbuild test robot
2016-09-06 17:28 ` Mike Christie
2016-08-01 1:18 kbuild 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=201608142002.0xj2aheW%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=axboe@kernel.dk \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchristi@redhat.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
all inboxes | Powered by JetHome®