From: Francesco Poli <frx@firenze.linux.it>
To: cpufreq@www.linux.org.uk
Subject: Re: Help with Installation
Date: Mon, 5 Apr 2004 22:20:15 +0200 [thread overview]
Message-ID: <20040405222015.4a560be1.frx@firenze.linux.it> (raw)
In-Reply-To: <20040404211144.GA9552@dominikbrodowski.de>
[-- Attachment #1.1: Type: text/plain, Size: 1388 bytes --]
On Sun, 4 Apr 2004 23:11:44 +0200 Dominik Brodowski wrote:
> Well, it might be usefull for you and others if someone (you?) could
> provide such up-to-date patches, and keeps 2.4. cpufreq up-to-date
> with recent 2.6. developments, as far as the latter is possible.
> However, none of the people currently active in cpufreq development
> seem to have sufficient time to do so. In case _you_ want to do it [as
> you said, it shouldn't be so difficult], please do so.
Perhaps it would be useful to setup a little script that
1) downloads the latest 2.4.x kernel (maybe via rsync)
2) modifies it using latest cpufreq from
http://ftp.linux.org.uk/pub/linux/cpufreq/
3) creates the patch against the unmodified kernel
4) gzips it and moves the resulting file in the right place
Such a script should be run daily (via cron) on ftp.linux.org.uk
This could perhaps work and provide up-to-date patches, as long as 2.4.x
cpufreq at http://ftp.linux.org.uk/pub/linux/cpufreq/ is kept up-to-date
with 2.6.x
Perhaps patchin.sh should be modified in order to use cp (or mv) rather
than ln -s
What do you think?
--
| 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-05 20:20 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
2004-04-04 21:11 ` Dominik Brodowski
2004-04-05 20:20 ` Francesco Poli [this message]
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=20040405222015.4a560be1.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