From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Li, Philip" <philip.li@intel.com>
Cc: "Wu, Fengguang" <fengguang.wu@intel.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: drivers/base/power/opp/cpu.c:120:5: error: redefinition of 'dev_pm_opp_set_sharing_cpus'
Date: Tue, 5 Apr 2016 12:50:50 +0530 [thread overview]
Message-ID: <20160405072050.GH20655@vireshk-i7> (raw)
In-Reply-To: <831EE4E5E37DCC428EB295A351E662491431DF0C@shsmsx102.ccr.corp.intel.com>
On 05-04-16, 07:18, Li, Philip wrote:
> Thanks, Viresh, will check why old commit is reported. On the other hand, I think even one config is not set, it should not introduce build error, which seems a valid failure.
What I am saying is that I couldn't reproduce the issue at my end and
the reason for that being the .config file doesn't have necessary
CONFIG_* options to build the code you reported failures for.
--
viresh
prev parent reply other threads:[~2016-04-05 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 1:34 drivers/base/power/opp/cpu.c:120:5: error: redefinition of 'dev_pm_opp_set_sharing_cpus' kbuild test robot
2016-04-05 3:10 ` Viresh Kumar
2016-04-05 7:18 ` Li, Philip
2016-04-05 7:20 ` Viresh Kumar [this message]
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=20160405072050.GH20655@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philip.li@intel.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.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