lkml.org 
[lkml]   [2016]   [Jan]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC PATCH 18/19] cpufreq: remove transition_lock
    On 11-01-16, 17:35, Juri Lelli wrote:
    > From: Michael Turquette <mturquette@baylibre.com>
    >
    > transition_lock was introduced to serialize cpufreq transition
    > notifiers. Instead of using a different lock for protecting concurrent
    > modifications of policy, it is better to require that callers of
    > transition notifiers implement appropriate locking (this is already the
    > case AFAICS). Removing transition_lock also simplifies current locking
    > scheme.

    So, are you saying that the reasoning mentioned in this patch are all
    wrong?

    commit 12478cf0c55e ("cpufreq: Make sure frequency transitions are
    serialized")

    --
    viresh

    \
     
     \ /
      Last update: 2016-01-12 13:21    [W:4.130 / U:0.108 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site