From: kbuild test robot <fengguang.wu@intel.com>
To: Thierry Reding <treding@nvidia.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Dave Airlie <airlied@redhat.com>
Subject: panel-samsung-s6e3ha2.c:undefined reference to `backlight_device_unregister'
Date: Mon, 12 Jun 2017 10:37:32 +0800 [thread overview]
Message-ID: <201706121030.IRRkFVGZ%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Hi Dave,
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: 32c1431eea4881a6b17bd7c639315010aeefa452
commit: ab6eb211b07a42a6346e284056422fd9a8576a99 Merge tag 'drm/panel/for-4.12-rc1' of git://anongit.freedesktop.org/tegra/linux into drm-next
date: 9 weeks ago
config: x86_64-randconfig-h0-06120933 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout ab6eb211b07a42a6346e284056422fd9a8576a99
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `s6e3ha2_remove':
>> panel-samsung-s6e3ha2.c:(.text+0x1a238e): undefined reference to `backlight_device_unregister'
drivers/built-in.o: In function `s6e3ha2_probe':
>> panel-samsung-s6e3ha2.c:(.text+0x1a257d): undefined reference to `backlight_device_register'
panel-samsung-s6e3ha2.c:(.text+0x1a2672): undefined reference to `backlight_device_unregister'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25521 bytes --]
next reply other threads:[~2017-06-12 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 2:37 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-04 10:39 kbuild test robot
[not found] <CGME20170528025312epcas4p38999224506eafbc82f2ed8b5a6ca340a@epcas4p3.samsung.com>
2017-05-28 2:52 ` kbuild test robot
2017-05-30 5:13 ` Hoegeun Kwon
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=201706121030.IRRkFVGZ%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=airlied@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=treding@nvidia.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®