From: Bas Mevissen <ml@basmevissen.nl>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: Dominik Brodowski <linux@brodo.de>, cpufreq@www.linux.org.uk
Subject: Re: cpufreq and 2.4.
Date: Mon, 18 Aug 2003 12:14:26 +0200 [thread overview]
Message-ID: <3F40A702.8040103@basmevissen.nl> (raw)
In-Reply-To: <20030818073948.GC18032@poupinou.org>
Ducrot Bruno wrote:
>
>>C) No documentation for 2.4. cpufreq user interfaces
>>As they're deprecated, I didn't explain them in the 2.6. kernel
>>Documentation (Documentation/cpu-freq/user.txt). However, if it really
>>should be documented well if it gets into the 2.4. stable series.
>>
>>D) Who?
>>Who is going to do C), and who will keep track of cpufreq-2.4.?
>
> My poor english prevent me to do C) (but perhaps a kind soul with good
> french knowledge and good english may assist me ?)
> I can track cpufreq-2.4 if really needed.
>
I guess my English is better than my French, so I'm happy to assist you
with C) :-))
I think it to be a good way to learn about cpufreq internals by writing
documentation for it.
Regards,
Bas.
next prev parent reply other threads:[~2003-08-18 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 15:35 cpufreq and 2.4 Dominik Brodowski
2003-08-18 7:39 ` Ducrot Bruno
2003-08-18 10:14 ` Bas Mevissen [this message]
2003-08-18 12:49 ` Ducrot Bruno
2003-08-18 13:21 ` Bas Mevissen
2003-08-18 10:47 ` Bas Mevissen
2003-08-18 10:57 ` Russell King
2003-08-18 12:13 ` Bas Mevissen
2003-08-18 18:10 ` Russell King
2003-08-18 18:00 ` Dominik Brodowski
2003-08-19 7:24 ` Ducrot Bruno
2003-08-19 8:58 ` Bas Mevissen
2003-08-19 8:45 ` Bas Mevissen
2003-08-19 11:42 ` Ducrot Bruno
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=3F40A702.8040103@basmevissen.nl \
--to=ml@basmevissen.nl \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
--cc=linux@brodo.de \
/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