Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1579367 > unrolled thread
| Started by | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| First post | 2017-02-13 04:20 +0100 |
| Last post | 2017-02-13 04:40 +0100 |
| Articles | 6 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency' Viresh Kumar <viresh.kumar@linaro.org> - 2017-02-13 04:20 +0100
Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency' Philip Li <philip.li@intel.com> - 2017-02-13 04:40 +0100
Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency' Philip Li <philip.li@intel.com> - 2017-02-13 04:40 +0100
Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency' Viresh Kumar <viresh.kumar@linaro.org> - 2017-02-13 05:00 +0100
Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency' Philip Li <philip.li@intel.com> - 2017-02-14 03:10 +0100
Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency' Viresh Kumar <viresh.kumar@linaro.org> - 2017-02-13 04:40 +0100
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Date | 2017-02-13 04:20 +0100 |
| Subject | Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency' |
| Message-ID | <taflg-6oZ-7@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Philip Li <philip.li@intel.com> |
|---|---|
| Date | 2017-02-13 04:40 +0100 |
| Message-ID | <tafEC-6vS-5@gated-at.bofh.it> |
| In reply to | #1579367 |
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 >
[toc] | [prev] | [next] | [standalone]
| From | Philip Li <philip.li@intel.com> |
|---|---|
| Date | 2017-02-13 04:40 +0100 |
| Message-ID | <tafEC-6vS-17@gated-at.bofh.it> |
| In reply to | #1579371 |
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
[toc] | [prev] | [next] | [standalone]
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Date | 2017-02-13 05:00 +0100 |
| Message-ID | <tafXX-6CA-1@gated-at.bofh.it> |
| In reply to | #1579379 |
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
[toc] | [prev] | [next] | [standalone]
| From | Philip Li <philip.li@intel.com> |
|---|---|
| Date | 2017-02-14 03:10 +0100 |
| Message-ID | <taAJ3-3JR-9@gated-at.bofh.it> |
| In reply to | #1579386 |
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
[toc] | [prev] | [next] | [standalone]
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Date | 2017-02-13 04:40 +0100 |
| Message-ID | <tafEC-6vS-19@gated-at.bofh.it> |
| In reply to | #1579371 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web