From: Ducrot Bruno <ducrot@poupinou.org>
To: Bas Mevissen <ml@basmevissen.nl>
Cc: Dominik Brodowski <linux@brodo.de>,
Bas Mevissen <sgm@basmevissen.nl>,
Cpufreq@www.linux.org.uk
Subject: Re: Cpufreq for 2.4: what is the best source?
Date: Thu, 21 Aug 2003 19:22:29 +0200 [thread overview]
Message-ID: <20030821172229.GC19292@poupinou.org> (raw)
In-Reply-To: <3F44A7DF.4040705@basmevissen.nl>
> (I mean setting the policy with e.g. echo userspace >/proc/cpufreq)
echo 0%100%userspace > /proc/cpufreq
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
prev parent reply other threads:[~2003-08-21 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 10:18 Cpufreq for 2.4: what is the best source? Bas Mevissen
2003-08-15 15:41 ` Dominik Brodowski
2003-08-15 16:53 ` Georg Sauthoff
2003-08-15 17:39 ` Russell King
2003-08-15 19:40 ` Dominik Brodowski
2003-08-18 9:37 ` Bas Mevissen
2003-08-18 17:53 ` Dominik Brodowski
2003-08-18 22:08 ` Bas Mevissen
2003-08-21 11:07 ` Bas Mevissen
2003-08-21 17:22 ` Ducrot Bruno [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=20030821172229.GC19292@poupinou.org \
--to=ducrot@poupinou.org \
--cc=Cpufreq@www.linux.org.uk \
--cc=linux@brodo.de \
--cc=ml@basmevissen.nl \
--cc=sgm@basmevissen.nl \
/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