From: Philip Li <philip.li@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
Date: Mon, 13 Feb 2017 11:41:34 +0800 [thread overview]
Message-ID: <20170213034134.GA9441@intel.com> (raw)
In-Reply-To: <20170213033455.GG8498@vireshk-i7>
On Mon, Feb 13, 2017 at 09:04:55AM +0530, Viresh Kumar wrote:
> On 13-02-17, 11:35, Philip Li wrote:
> > On Mon, Feb 13, 2017 at 08:43:38AM +0530, Viresh Kumar wrote:
> > > On 13-02-17, 03:35, kbuild test robot wrote:
> > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > > > head: 1ce42845f987e92eabfc6e026d44d826c25c74a5
> > > > commit: 655c9df961751ce21466f6e97e8033932c27a675 PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
> > > > date: 1 year ago
> > >
> > > And we are seeing these bogus reports again :(
> > thanks for feedback, do you mean this is a wrongly reported issue, like the issue can't
> > be reproduced or the issue was fixed already?
>
> Look at the date of the patch above: "1 year ago".
got it, i will check this part to see why reporting on 1 year old commit.
>
> I have also received 7-8 more mails for the OPP framework and they are all bogus
> as well.
on the other side, this is a build issue from randconfig, looks the failure exists on linus/master
head 1ce4284, and caused by 655c9df commit. Not sure whether you can reproduce it, or if it is not
a real issue, we can further follow up to fix false warning.
>
> --
> viresh
next prev parent reply other threads:[~2017-02-13 3:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 19:35 drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency' kbuild test robot
2017-02-13 3:13 ` Viresh Kumar
2017-02-13 3:35 ` Philip Li
2017-02-13 3:34 ` Viresh Kumar
2017-02-13 3:41 ` Philip Li [this message]
2017-02-13 3:57 ` Viresh Kumar
2017-02-14 2:07 ` Philip Li
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=20170213034134.GA9441@intel.com \
--to=philip.li@intel.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.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