From: kbuild test robot <fengguang.wu@intel.com>
To: Len Brown <len.brown@intel.com>
Cc: kbuild-all@01.org, linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [acpi:release 3/3] intel_idle.c:undefined reference to `__udivdi3'
Date: Thu, 24 Mar 2016 14:25:45 +0800 [thread overview]
Message-ID: <201603241443.6LBLekqw%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux.git release
head: 1664c8b16a75e9f73f4f40186c0c843bbf7dbde8
commit: 1664c8b16a75e9f73f4f40186c0c843bbf7dbde8 [3/3] intel_idle: add BXT support
config: i386-randconfig-n0-03241107 (attached as .config)
reproduce:
git checkout 1664c8b16a75e9f73f4f40186c0c843bbf7dbde8
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `intel_idle_init':
>> intel_idle.c:(.init.text+0x16a3): undefined reference to `__udivdi3'
intel_idle.c:(.init.text+0x16e4): undefined reference to `__udivdi3'
intel_idle.c:(.init.text+0x1725): undefined reference to `__udivdi3'
intel_idle.c:(.init.text+0x1766): undefined reference to `__udivdi3'
intel_idle.c:(.init.text+0x17ab): undefined reference to `__udivdi3'
---
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: 25000 bytes --]
next reply other threads:[~2016-03-24 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 6:25 kbuild test robot [this message]
2016-03-24 6:55 ` [acpi:release 3/3] intel_idle.c:undefined reference to `__udivdi3' Zheng, Lv
-- strict thread matches above, loose matches on Subject: below --
2016-03-24 8:40 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=201603241443.6LBLekqw%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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).