On Tue, Oct 22, 2019 at 12:07 PM Viresh Kumar wrote:
>
> On 22-10-19, 11:46, Rafael J. Wysocki wrote:
> > On Tue, Oct 22, 2019 at 4:25 AM Viresh Kumar
> > wrote:
> > >
> > > On 21-10-19, 14:28, Sudeep Holla wrote:
> > > > Commit 099967699ad9 ("cpufreq: Cancel policy update work scheduled
> > >
On 22-10-19, 11:46, Rafael J. Wysocki wrote:
> On Tue, Oct 22, 2019 at 4:25 AM Viresh Kumar wrote:
> >
> > On 21-10-19, 14:28, Sudeep Holla wrote:
> > > Commit 099967699ad9 ("cpufreq: Cancel policy update work scheduled before
> > > freeing")
> > > added cancel_work_sync(policy->update) after the
On Tue, Oct 22, 2019 at 4:25 AM Viresh Kumar wrote:
>
> On 21-10-19, 14:28, Sudeep Holla wrote:
> > Commit 099967699ad9 ("cpufreq: Cancel policy update work scheduled before
> > freeing")
> > added cancel_work_sync(policy->update) after the frequency QoS were
> > removed. We can cancel the work j
On 21-10-19, 14:28, Sudeep Holla wrote:
> Commit 099967699ad9 ("cpufreq: Cancel policy update work scheduled before
> freeing")
> added cancel_work_sync(policy->update) after the frequency QoS were
> removed. We can cancel the work just after taking the last CPU in the
> policy offline and unregis
Commit 099967699ad9 ("cpufreq: Cancel policy update work scheduled before
freeing")
added cancel_work_sync(policy->update) after the frequency QoS were
removed. We can cancel the work just after taking the last CPU in the
policy offline and unregistering the notifiers as policy->update cannot
be s
5 matches
Mail list logo