* drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
@ 2017-02-12 19:35 kbuild test robot
2017-02-13 3:13 ` Viresh Kumar
0 siblings, 1 reply; 7+ messages in thread
From: kbuild test robot @ 2017-02-12 19:35 UTC (permalink / raw)
To: Viresh Kumar; +Cc: kbuild-all, linux-kernel, Rafael J. Wysocki, Stephen Boyd
[-- Attachment #1: Type: text/plain, Size: 11060 bytes --]
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
config: x86_64-randconfig-x008-201707 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout 655c9df961751ce21466f6e97e8033932c27a675
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/base/power/opp/core.c:124:15: error: redefinition of 'dev_pm_opp_get_voltage'
unsigned long dev_pm_opp_get_voltage(struct dev_pm_opp *opp)
^~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:67:29: note: previous definition of 'dev_pm_opp_get_voltage' was here
static inline unsigned long dev_pm_opp_get_voltage(struct dev_pm_opp *opp)
^~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:156:15: error: redefinition of 'dev_pm_opp_get_freq'
unsigned long dev_pm_opp_get_freq(struct dev_pm_opp *opp)
^~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:72:29: note: previous definition of 'dev_pm_opp_get_freq' was here
static inline unsigned long dev_pm_opp_get_freq(struct dev_pm_opp *opp)
^~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:191:6: error: redefinition of 'dev_pm_opp_is_turbo'
bool dev_pm_opp_is_turbo(struct dev_pm_opp *opp)
^~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:77:20: note: previous definition of 'dev_pm_opp_is_turbo' was here
static inline bool dev_pm_opp_is_turbo(struct dev_pm_opp *opp)
^~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:215:15: error: redefinition of 'dev_pm_opp_get_max_clock_latency'
unsigned long dev_pm_opp_get_max_clock_latency(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:87:29: note: previous definition of 'dev_pm_opp_get_max_clock_latency' was here
static inline unsigned long dev_pm_opp_get_max_clock_latency(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
unsigned long dev_pm_opp_get_max_volt_latency(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:92:29: note: previous definition of 'dev_pm_opp_get_max_volt_latency' was here
static inline unsigned long dev_pm_opp_get_max_volt_latency(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:305:20: error: redefinition of 'dev_pm_opp_get_suspend_opp'
struct dev_pm_opp *dev_pm_opp_get_suspend_opp(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:97:34: note: previous definition of 'dev_pm_opp_get_suspend_opp' was here
static inline struct dev_pm_opp *dev_pm_opp_get_suspend_opp(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:329:5: error: redefinition of 'dev_pm_opp_get_opp_count'
int dev_pm_opp_get_opp_count(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:82:19: note: previous definition of 'dev_pm_opp_get_opp_count' was here
static inline int dev_pm_opp_get_opp_count(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:382:20: error: redefinition of 'dev_pm_opp_find_freq_exact'
struct dev_pm_opp *dev_pm_opp_find_freq_exact(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:102:34: note: previous definition of 'dev_pm_opp_find_freq_exact' was here
static inline struct dev_pm_opp *dev_pm_opp_find_freq_exact(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:431:20: error: redefinition of 'dev_pm_opp_find_freq_ceil'
struct dev_pm_opp *dev_pm_opp_find_freq_ceil(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:114:34: note: previous definition of 'dev_pm_opp_find_freq_ceil' was here
static inline struct dev_pm_opp *dev_pm_opp_find_freq_ceil(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:481:20: error: redefinition of 'dev_pm_opp_find_freq_floor'
struct dev_pm_opp *dev_pm_opp_find_freq_floor(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:108:34: note: previous definition of 'dev_pm_opp_find_freq_floor' was here
static inline struct dev_pm_opp *dev_pm_opp_find_freq_floor(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:696:6: error: redefinition of 'dev_pm_opp_remove'
void dev_pm_opp_remove(struct device *dev, unsigned long freq)
^~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:126:20: note: previous definition of 'dev_pm_opp_remove' was here
static inline void dev_pm_opp_remove(struct device *dev, unsigned long freq)
^~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:972:5: error: redefinition of 'dev_pm_opp_set_supported_hw'
int dev_pm_opp_set_supported_hw(struct device *dev, const u32 *versions,
^~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:146:19: note: previous definition of 'dev_pm_opp_set_supported_hw' was here
static inline int dev_pm_opp_set_supported_hw(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:1032:6: error: redefinition of 'dev_pm_opp_put_supported_hw'
void dev_pm_opp_put_supported_hw(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:153:20: note: previous definition of 'dev_pm_opp_put_supported_hw' was here
static inline void dev_pm_opp_put_supported_hw(struct device *dev) {}
^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:1083:5: error: redefinition of 'dev_pm_opp_set_prop_name'
int dev_pm_opp_set_prop_name(struct device *dev, const char *name)
^~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:155:19: note: previous definition of 'dev_pm_opp_set_prop_name' was here
static inline int dev_pm_opp_set_prop_name(struct device *dev, const char *name)
^~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:1140:6: error: redefinition of 'dev_pm_opp_put_prop_name'
void dev_pm_opp_put_prop_name(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:160:20: note: previous definition of 'dev_pm_opp_put_prop_name' was here
static inline void dev_pm_opp_put_prop_name(struct device *dev) {}
^~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:1189:5: error: redefinition of 'dev_pm_opp_set_regulator'
int dev_pm_opp_set_regulator(struct device *dev, const char *name)
^~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
include/linux/pm_opp.h:162:19: note: previous definition of 'dev_pm_opp_set_regulator' was here
static inline int dev_pm_opp_set_regulator(struct device *dev, const char *name)
^~~~~~~~~~~~~~~~~~~~~~~~
drivers/base/power/opp/core.c:1248:6: error: redefinition of 'dev_pm_opp_put_regulator'
void dev_pm_opp_put_regulator(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/base/power/opp/opp.h:21:0,
from drivers/base/power/opp/core.c:24:
vim +/dev_pm_opp_get_max_volt_latency +241 drivers/base/power/opp/core.c
209 * @dev: device for which we do this operation
210 *
211 * Return: This function returns the max clock latency in nanoseconds.
212 *
213 * Locking: This function takes rcu_read_lock().
214 */
> 215 unsigned long dev_pm_opp_get_max_clock_latency(struct device *dev)
216 {
217 struct device_opp *dev_opp;
218 unsigned long clock_latency_ns;
219
220 rcu_read_lock();
221
222 dev_opp = _find_device_opp(dev);
223 if (IS_ERR(dev_opp))
224 clock_latency_ns = 0;
225 else
226 clock_latency_ns = dev_opp->clock_latency_ns_max;
227
228 rcu_read_unlock();
229 return clock_latency_ns;
230 }
231 EXPORT_SYMBOL_GPL(dev_pm_opp_get_max_clock_latency);
232
233 /**
234 * dev_pm_opp_get_max_volt_latency() - Get max voltage latency in nanoseconds
235 * @dev: device for which we do this operation
236 *
237 * Return: This function returns the max voltage latency in nanoseconds.
238 *
239 * Locking: This function takes rcu_read_lock().
240 */
> 241 unsigned long dev_pm_opp_get_max_volt_latency(struct device *dev)
242 {
243 struct device_opp *dev_opp;
244 struct dev_pm_opp *opp;
---
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: 29059 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
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
0 siblings, 1 reply; 7+ messages in thread
From: Viresh Kumar @ 2017-02-13 3:13 UTC (permalink / raw)
To: kbuild test robot
Cc: kbuild-all, linux-kernel, Rafael J. Wysocki, Stephen Boyd
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 :(
--
viresh
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
2017-02-13 3:13 ` Viresh Kumar
@ 2017-02-13 3:35 ` Philip Li
2017-02-13 3:34 ` Viresh Kumar
0 siblings, 1 reply; 7+ messages in thread
From: Philip Li @ 2017-02-13 3:35 UTC (permalink / raw)
To: Viresh Kumar
Cc: kbuild test robot, kbuild-all, linux-kernel, Rafael J. Wysocki,
Stephen Boyd
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?
>
> --
> viresh
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
2017-02-13 3:35 ` Philip Li
@ 2017-02-13 3:34 ` Viresh Kumar
2017-02-13 3:41 ` Philip Li
0 siblings, 1 reply; 7+ messages in thread
From: Viresh Kumar @ 2017-02-13 3:34 UTC (permalink / raw)
To: Philip Li
Cc: kbuild test robot, kbuild-all, linux-kernel, Rafael J. Wysocki,
Stephen Boyd
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".
I have also received 7-8 more mails for the OPP framework and they are all bogus
as well.
--
viresh
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
2017-02-13 3:34 ` Viresh Kumar
@ 2017-02-13 3:41 ` Philip Li
2017-02-13 3:57 ` Viresh Kumar
0 siblings, 1 reply; 7+ messages in thread
From: Philip Li @ 2017-02-13 3:41 UTC (permalink / raw)
To: Viresh Kumar
Cc: kbuild test robot, kbuild-all, linux-kernel, Rafael J. Wysocki,
Stephen Boyd
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
2017-02-13 3:41 ` Philip Li
@ 2017-02-13 3:57 ` Viresh Kumar
2017-02-14 2:07 ` Philip Li
0 siblings, 1 reply; 7+ messages in thread
From: Viresh Kumar @ 2017-02-13 3:57 UTC (permalink / raw)
To: Philip Li
Cc: kbuild test robot, kbuild-all, linux-kernel, Rafael J. Wysocki,
Stephen Boyd
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.
--
viresh
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
2017-02-13 3:57 ` Viresh Kumar
@ 2017-02-14 2:07 ` Philip Li
0 siblings, 0 replies; 7+ messages in thread
From: Philip Li @ 2017-02-14 2:07 UTC (permalink / raw)
To: Viresh Kumar
Cc: kbuild test robot, kbuild-all, linux-kernel, Rafael J. Wysocki,
Stephen Boyd
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-02-14 2:05 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2017-02-13 3:57 ` Viresh Kumar
2017-02-14 2:07 ` Philip Li
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox