From: Xavier Bestel <xavier.bestel@free.fr>
To: Dominik Brodowski <linux@brodo.de>
Cc: torvalds@transmeta.com, hpa@transmeta.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
cpufreq@www.linux.org.uk
Subject: Re: [PATCH][2.5.35] CPUfreq documentation (4/5)
Date: 17 Sep 2002 12:19:37 +0200 [thread overview]
Message-ID: <1032257979.3070.29.camel@nomade> (raw)
In-Reply-To: <20020917113547.H25385@brodo.de>
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
> +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
> +CPUFREQ_ALL_CPUS for all CPUs; and max_cpu_freq the maximum supported
> +CPU frequency. This value is given for informational purposes only.
- Why choosing a void* ? that doesn't validate type ..
- 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.
next prev parent reply other threads:[~2002-09-17 10:14 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 [this message]
2002-09-17 11:00 ` Russell King
2002-09-17 14:39 ` [PATCH] " Dominik Brodowski
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=1032257979.3070.29.camel@nomade \
--to=xavier.bestel@free.fr \
--cc=cpufreq@www.linux.org.uk \
--cc=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=torvalds@transmeta.com \
/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