linux-kernel - Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170213034134.GA9441@intel.com>
Date:   Mon, 13 Feb 2017 11:41:34 +0800
From:   Philip Li <philip.li@...el.com>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     kbuild test robot <fengguang.wu@...el.com>, kbuild-all@...org,
        linux-kernel@...r.kernel.org,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Stephen Boyd <sboyd@...eaurora.org>
Subject: Re: drivers/base/power/opp/core.c:241:15: error: redefinition of
 'dev_pm_opp_get_max_volt_latency'

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