From: Francesco Poli <frx@firenze.linux.it>
To: cpufreq@www.linux.org.uk
Subject: Re: Help with Installation
Date: Sun, 4 Apr 2004 19:57:30 +0200 [thread overview]
Message-ID: <20040404195730.6fac6745.frx@firenze.linux.it> (raw)
In-Reply-To: <20040403172242.D5553@flint.arm.linux.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1052 bytes --]
On Sat, 3 Apr 2004 17:22:42 +0100 Russell King wrote:
> We don't have the (massive) resources to be able to generate a patch
> for every single kernel version which someone may want to apply the
> cpufreq code to from the CVS.
Well, I think that a patch against the latest 2.4.x kernel and one
against the latest 2.4.x pre-release (2.4.x-prex or 2.4.x-rcx) would
suffice.
Adapting one such patch in order to apply it to some less recent 2.4.x
kernel version is not so difficult.
At least, that was my personal experience: I successfully applied
cpufreq-2.4.22-pre6-1.gz (by hand-editing the diff file) to 2.4.22,
2.4.23, 2.4.24 and 2.4.25.
Adapting a hypothetical cpufreq-2.4.25-1.gz to the same kernel versions
should not be more challenging...
What's your opinion?
--
| 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
next prev parent reply other threads:[~2004-04-04 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 13:42 Help with Installation Ozeki San
2004-04-03 14:50 ` Bruno Ducrot
2004-04-03 15:16 ` Francesco Poli
2004-04-03 16:22 ` Russell King
2004-04-04 17:57 ` Francesco Poli [this message]
2004-04-04 21:11 ` Dominik Brodowski
2004-04-05 20:20 ` Francesco Poli
2004-04-05 21:06 ` Russell King
2004-04-06 21:01 ` Francesco Poli
2004-04-07 7:11 ` Russell King
2004-04-07 20:26 ` Francesco Poli
2004-04-05 21:11 ` Dominik Brodowski
2004-04-06 8:25 ` Bruno Ducrot
2004-04-06 8:47 ` Bruno Ducrot
2004-04-06 21:50 ` Francesco Poli
2004-04-07 16:18 ` Bruno Ducrot
2004-04-06 21:48 ` Francesco Poli
2004-04-06 22:00 ` 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=20040404195730.6fac6745.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.