From: Francesco Poli <frx@firenze.linux.it>
To: CpuFreq <cpufreq@www.linux.org.uk>
Subject: Where are the 2.4.x patches?
Date: Tue, 6 Jan 2004 22:04:25 +0100 [thread overview]
Message-ID: <20040106220425.7e6db911.frx@firenze.linux.it> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 621 bytes --]
Hi everybody! :)
Since http://www.codemonkey.org.uk/projects/cpufreq/ has been
unavailable for a fairly long time, can anyone point me to a web (or
ftp) site where I can find a cpufreq patch against the 2.4.24 kernel?
TNX for your time (and for the great job in cpufreq development!).
:-)
Please reply to the list as I'm a subscriber.
--
| GnuPG Key ID = DD6DFCF4 | You're compiling a program
Francesco | Key fingerprint = | and, all of a sudden, boom!
Poli | C979 F34B 27CE 5CD8 DC12 | -- from APT HOWTO,
| 31B5 78F4 279B DD6D FCF4 | version 1.8.0
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
reply other threads:[~2004-01-06 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040106220425.7e6db911.frx@firenze.linux.it \
--to=frx@firenze.linux.it \
--cc=cpufreq@www.linux.org.uk \
/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