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] [day] [month] [year] [list]
Message-ID: <20170214020729.GB10346@intel.com>
Date:   Tue, 14 Feb 2017 10:07:29 +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:27:59AM +0530, Viresh Kumar wrote:
> On 13-02-17, 11:41, Philip Li wrote:
> > 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.
> 
> I don't think so. This is what your report says:
> 
> reproduce:
>         git checkout 655c9df961751ce21466f6e97e8033932c27a675
>         # save the attached .config to linux build tree
>         make ARCH=x86_64
> 
> It never said that you can checkout 1ce4284 and reproduce this.
> 
> Can you try to reproduce it on 1ce4284? I am sure you wouldn't find anything.
ah, it looks like a false reporting, both commits are ok. 

I will follow up to fix this. sorry for inconvenience caused.

> 
> -- 
> viresh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ