Re: [PATCH v4 1/1] PM / OPP: Fix get sharing cpus when hotplug is used

[Viresh Kumar <viresh.kumar@linaro.org>]

On 31-07-17, 20:50, Rafael J. Wysocki wrote:
> On Mon, Jul 31, 2017 at 5:12 PM, Waldemar Rymarkiewicz
> <waldemar.rymarkiewicz@gmail.com> wrote:
> > On 31 July 2017 at 13:14, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> >> On Sunday, July 30, 2017 10:54:30 PM kbuild test robot wrote:
> >>> Hi Waldemar,
> >>>
> >>> [auto build test ERROR on pm/linux-next]
> >>> [also build test ERROR on v4.13-rc2 next-20170728]
> >>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> >>
> >> OK, I'm dropping this commit.
> >>
> >> Please make sure that the problem is fixed before sending a new version of it.
> >
> > I am a bit confused, it was already fixed and sent out in v5 [1], but
> > I see v5 is in 'Not Applicable, archived' state. Why?
> >
> > [1] https://patchwork.kernel.org/patch/9866525/
> 
> Because it was applied and still broke.

Not actually.

The bug report *wasn't* reported for the patch you applied, but how would be the
build go if V4 is applied on top of pm/linux-next. And so buildbot replied to
this thread.

It can sometimes get a bit confusing seriously, I have to read it very carefully
today after the discussions you two had :)

You can re-apply the commit as that was doing the right thing:

commit 63a48cf920c0 ("PM / OPP: Fix get sharing CPUs when hotplug is used")

@Fengguang: We need to somehow indicate (in BOLD/CAPS?) that the report isn't
for a commit in the tree. Yeah, you would normally include the commit sha in
that case and so we can actually distinguish between the two cases. But
practically, people are getting confused unless they read it very very
carefully. Thanks for the great job btw :)

-- 
viresh