All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jane Li <jiel@marvell.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] cpufreq: Fix timer/workqueue corruption by protecting reading governor_enabled
Date: Fri, 3 Jan 2014 17:19:19 +0800	[thread overview]
Message-ID: <52C68097.7070508@marvell.com> (raw)
In-Reply-To: <CAKohpomWCpxCSFfG601Pc_FKcbZ3J7G2nsBABMb8qqQJ38h1cg@mail.gmail.com>


On 01/03/2014 02:50 PM, Viresh Kumar wrote:
> On 3 January 2014 12:14,  <jiel@marvell.com> wrote:
>> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
>> index dc196bb..15c62df 100644
>> --- a/include/linux/cpufreq.h
>> +++ b/include/linux/cpufreq.h
>> @@ -389,6 +389,7 @@ int __cpufreq_driver_target(struct cpufreq_policy *policy,
>>                                     unsigned int relation);
>>   int cpufreq_register_governor(struct cpufreq_governor *governor);
>>   void cpufreq_unregister_governor(struct cpufreq_governor *governor);
>> +extern struct mutex cpufreq_governor_lock;
>>
>>   /* CPUFREQ DEFAULT GOVERNOR */
>>   /*
> Move this to cpufreq_governor.h instead. I don't want this to be available
> for everybody to use it.

OK. Have pushed PATCH v4. Please review again.

Thanks!

      reply	other threads:[~2014-01-03  9:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  6:44 [PATCH v3] cpufreq: Fix timer/workqueue corruption by protecting reading governor_enabled jiel
2014-01-03  6:44 ` jiel
2014-01-03  6:50 ` Viresh Kumar
2014-01-03  9:19   ` Jane Li [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52C68097.7070508@marvell.com \
    --to=jiel@marvell.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.