The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Ingo Molnar <mingo@elte.hu>
Cc: Esben Nielsen <simlo@phys.au.dk>, linux-kernel@vger.kernel.org
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.12-rc6-V0.7.47-20
Date: Tue, 07 Jun 2005 18:30:33 +0200	[thread overview]
Message-ID: <42A5CBA9.3030704@stud.feec.vutbr.cz> (raw)
In-Reply-To: <20050607160400.GA9904@elte.hu>

Ingo Molnar wrote:
> * Esben Nielsen <simlo@phys.au.dk> wrote:
> 
> 
>>Hey,
>> This is an old problem of cpu_freq.c not compiling. I (re)send a fix 
>>for it. This time as a real patch...
> 
> 
> thanks - i've applied it and have released the -47-27 patch with this 
> fix included.

Yes, that's an obviously safe fix.
I asked on the cpufreq mailing list about this lock. Here's the answer I 
got from Dominik Brodowski:

Dominik Brodowski wrote:
> On Wed, Jun 01, 2005 at 06:57:12PM +0200, Michal Schmidt wrote:
> 
>> Hello,
>> I think that it's not necessary to take the policy->lock in cpufreq_add_dev.
>> Am I missing something? What is the lock supposed to protect from?
> 
> 
> Well, indeed it is not necessary to take the policy->lock, although it
> doesn't do any harm AFAICS. I added it to make sure that _all_ accesses to
> the data is protected by the lock, how serialized they may ever be..
> 
> Thanks,
> 	Dominik


Michal

  reply	other threads:[~2005-06-07 16:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 11:04 [patch] Real-Time Preemption, -RT-2.6.12-rc6-V0.7.47-20 Ingo Molnar
2005-06-07 11:31 ` Steven Rostedt
2005-06-07 11:34   ` Ingo Molnar
2005-06-07 11:51 ` Michal Schmidt
2005-06-07 12:05   ` Ingo Molnar
2005-06-07 15:54 ` Esben Nielsen
2005-06-07 16:04   ` Ingo Molnar
2005-06-07 16:30     ` Michal Schmidt [this message]
2005-06-07 17:30     ` Peter Zijlstra
2005-06-07 19:05       ` Ingo Molnar
2005-06-07 19:02 ` Michal Schmidt
2005-06-07 19:25   ` Ingo Molnar

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=42A5CBA9.3030704@stud.feec.vutbr.cz \
    --to=xschmi00@stud.feec.vutbr.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=simlo@phys.au.dk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox