public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: torvalds@transmeta.com, hpa@transmeta.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	cpufreq@www.linux.org.uk
Subject: [PATCH] Re: CPUfreq documentation (4/5)
Date: Tue, 17 Sep 2002 16:39:34 +0200	[thread overview]
Message-ID: <20020917163933.A853@brodo.de> (raw)
In-Reply-To: <1032257979.3070.29.camel@nomade>; from xavier.bestel@free.fr on Tue, Sep 17, 2002 at 12:19:37PM +0200

Hi Xavier,

Thanks for the two corrections!

On Tue, Sep 17, 2002 at 12:19:37PM +0200, Xavier Bestel wrote:
> Le mar 17/09/2002 à 11:35, Dominik Brodowski a écrit :
> 
> > +The third argument, a void *pointer, points to a struct cpufreq_freqs
> > +consisting of five values: cpu, min, max, policy and max_cpu_freq. Min 
> 
> - The struct cpufreq_freqs actually consists of only three values (cpu,
> old, new). The five values you cite here are in the struct
> cpufreq_policy.

	Dominik

--- linux/Documentation/cpufreq.original	Tue Sep 17 16:36:32 2002
+++ linux/Documentation/cpufreq	Tue Sep 17 16:37:09 2002
@@ -76,7 +76,6 @@
 ---------------------------------
     Note that you can only switch the speed of two logical CPUs at
     once - but each phyiscal CPU may have different throttling levels.
-    Unfortunately, the cpu_khz value 
 
 
 PowerNow! K6:
@@ -222,7 +221,7 @@
 
 The phase is specified in the second argument to the notifier.
 
-The third argument, a void *pointer, points to a struct cpufreq_freqs
+The third argument, a void *pointer, points to a struct cpufreq_policy
 consisting of five values: cpu, min, max, policy and max_cpu_freq. Min 
 and max are the lower and upper frequencies (in kHz) of the new
 policy, policy the new policy, cpu the number of the affected CPU or

      parent reply	other threads:[~2002-09-17 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17  9:35 [PATCH][2.5.35] CPUfreq documentation (4/5) Dominik Brodowski
2002-09-17 10:03 ` Xavier Bestel
2002-09-17 10:19 ` Xavier Bestel
2002-09-17 11:00   ` Russell King
2002-09-17 14:39   ` Dominik Brodowski [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=20020917163933.A853@brodo.de \
    --to=linux@brodo.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=hpa@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=xavier.bestel@free.fr \
    /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