Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: lkp@intel.com (kbuild test robot)
Subject: [PATCH v12 2/5] gennvm: Generic NVM manager
Date: Wed, 28 Oct 2015 05:18:51 +0800	[thread overview]
Message-ID: <201510280545.eLwfUREZ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445957719-5368-3-git-send-email-m@bjorling.me>

Hi Matias,

[auto build test ERROR on next-20151022 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Matias-Bj-rling/Support-for-Open-Channel-SSDs/20151027-230440
config: i386-allyesconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/built-in.o: In function `addr_to_generic_mode':
>> gennvm.c:(.text+0x88e078): undefined reference to `__umoddi3'
>> gennvm.c:(.text+0x88e090): undefined reference to `__udivdi3'
   gennvm.c:(.text+0x88e0a1): undefined reference to `__umoddi3'
   gennvm.c:(.text+0x88e0c7): undefined reference to `__udivdi3'
   gennvm.c:(.text+0x88e0d5): undefined reference to `__umoddi3'
   gennvm.c:(.text+0x88e10d): undefined reference to `__udivdi3'
   gennvm.c:(.text+0x88e11b): undefined reference to `__umoddi3'
   gennvm.c:(.text+0x88e144): undefined reference to `__udivdi3'
   drivers/built-in.o: In function `gennvm_block_map':
   gennvm.c:(.text+0x88e298): undefined reference to `__udivdi3'
   gennvm.c:(.text+0x88e2c9): undefined reference to `__udivdi3'
   drivers/built-in.o: In function `gennvm_erase_blk':
   gennvm.c:(.text+0x88e459): undefined reference to `__umoddi3'

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/octet-stream
Size: 51860 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20151028/122298a6/attachment-0001.obj>

  parent reply	other threads:[~2015-10-27 21:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 14:55 [PATCH v12 0/5] Support for Open-Channel SSDs Matias Bjørling
2015-10-27 14:55 ` [PATCH v12 1/5] lightnvm: " Matias Bjørling
2015-10-27 16:15   ` [PATCH] lightnvm: fix memdup_user.cocci warnings kbuild test robot
2015-10-27 16:15   ` [PATCH v12 1/5] lightnvm: Support for Open-Channel SSDs kbuild test robot
2015-10-27 14:55 ` [PATCH v12 2/5] gennvm: Generic NVM manager Matias Bjørling
2015-10-27 20:43   ` kbuild test robot
2015-10-27 21:18   ` kbuild test robot [this message]
2015-10-27 14:55 ` [PATCH v12 3/5] rrpc: Round-robin sector target with cost-based gc Matias Bjørling
2015-10-27 23:44   ` kbuild test robot
2015-10-27 14:55 ` [PATCH v12 4/5] null_nvm: LightNVM test driver Matias Bjørling
2015-10-27 22:24   ` kbuild test robot
2015-10-27 14:55 ` [PATCH v12 5/5] nvme: LightNVM support Matias Bjørling

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=201510280545.eLwfUREZ%fengguang.wu@intel.com \
    --to=lkp@intel.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