From: kbuild test robot <fengguang.wu@intel.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Sasha Levin <sasha.levin@oracle.com>
Subject: undefined reference to `dib3000mc_pid_parse'
Date: Tue, 8 Dec 2015 12:30:08 +0800 [thread overview]
Message-ID: <201512081206.JWRR0iIe%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
Hi Kirill,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 62ea1ec5e17fe36e2c728bc534f9f78b216dfe83
commit: 51b97e354ba9fce1890cf38ecc754aa49677fc89 kernel: use the gnu89 standard explicitly
date: 1 year, 1 month ago
config: x86_64-randconfig-a0-12081135 (attached as .config)
reproduce:
git checkout 51b97e354ba9fce1890cf38ecc754aa49677fc89
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `dibusb_dib3000mc_frontend_attach':
>> (.text+0x207627): undefined reference to `dib3000mc_pid_parse'
drivers/built-in.o: In function `dibusb_dib3000mc_frontend_attach':
>> (.text+0x20762f): undefined reference to `dib3000mc_pid_control'
drivers/built-in.o: In function `dibusb_dib3000mc_tuner_attach':
(.text+0x20773a): undefined reference to `dib3000mc_get_tuner_i2c_master'
drivers/built-in.o: In function `dibusb_dib3000mc_tuner_attach':
>> (.text+0x207822): undefined reference to `dib3000mc_set_config'
---
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: 21027 bytes --]
next reply other threads:[~2015-12-08 4:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 4:30 kbuild test robot [this message]
2016-02-20 11:49 kbuild test robot
2016-08-28 8:15 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=201512081206.JWRR0iIe%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.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®