From: kbuild test robot <fengguang.wu@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: kbuild-all@01.org, linux-pm@vger.kernel.org
Subject: [vireshk:opp/redesign 20/33] fair_share.c:(.text+0x2b5): multiple definition of `dev_pm_opp_unregister_notifier'
Date: Fri, 2 Dec 2016 20:26:49 +0800 [thread overview]
Message-ID: <201612022046.DtplDrll%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
tree: https://git.linaro.org/people/vireshk/linux opp/redesign
head: fbf8f0c337a7cfcd4cb67865b5ea710e69c21f1f
commit: 28475c4b5d76a2eef9b35fa198545403e07e1461 [20/33] PM / OPP: Don't expose srcu_head to register notifiers
config: x86_64-randconfig-i0-201648 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout 28475c4b5d76a2eef9b35fa198545403e07e1461
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/thermal/fair_share.o: In function `dev_pm_opp_unregister_notifier':
>> fair_share.c:(.text+0x2b5): multiple definition of `dev_pm_opp_unregister_notifier'
drivers/thermal/thermal_core.o:thermal_core.c:(.text+0x200d): first defined here
drivers/thermal/step_wise.o: In function `dev_pm_opp_unregister_notifier':
step_wise.c:(.text+0x3c8): multiple definition of `dev_pm_opp_unregister_notifier'
drivers/thermal/thermal_core.o:thermal_core.c:(.text+0x200d): first defined here
---
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: 24532 bytes --]
next reply other threads:[~2016-12-02 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 12:26 kbuild test robot [this message]
2016-12-02 14:13 ` [vireshk:opp/redesign 20/33] fair_share.c:(.text+0x2b5): multiple definition of `dev_pm_opp_unregister_notifier' Viresh Kumar
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=201612022046.DtplDrll%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-pm@vger.kernel.org \
--cc=viresh.kumar@linaro.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