From: Ducrot Bruno <ducrot@poupinou.org>
To: gojyo <guardian@killamail.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: kernel 2.4.20
Date: Tue, 13 Jan 2004 16:51:28 +0100 [thread overview]
Message-ID: <20040113155128.GM14031@poupinou.org> (raw)
In-Reply-To: <20040113111042.DB6113958@sitemail.everyone.net>
On Tue, Jan 13, 2004 at 03:10:42AM -0800, gojyo wrote:
> I need to patch a 2.4.20 kernel; however, with the last release of cpufreq for 2.4 kernels I have lot of patch errors. In the ftp archive I can't understand which version I need, can you help me please? Which release do I need for 2.4.20 kernel?
You have 2 solutions:
1- integrate by hand the rejected patch,
2- use cvs with:
cvs -d:pserver:cvs@pubcvs.arm.linux.org.uk:/mnt/src/cvsroot co -rlinux_2_4_old cpufreq
which was done before the new core for 2.4 was updated (first done for
linux-2.4.21 IIRC).
BUT this one is old and contains well known bugs that have been fixed.
If I were you, I will integrate by hand the latest (that should be not
so hard).
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-01-13 15:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 11:10 kernel 2.4.20 gojyo
2004-01-13 15:51 ` Ducrot Bruno [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-24 3:19 Kernel 2.4.20 David Munn
2003-07-24 4:57 ` Jeremy Utley
2003-07-24 8:01 ` Riley Williams
2003-05-23 6:19 kernel 2.4.20 Gurpreet Singh (SCM)
2003-05-23 18:51 ` Jan Knutar
2003-02-25 3:48 Change -mcpu option for VR41xx Yoichi Yuasa
2003-02-25 7:58 ` Kernel 2.4.20 jeff
2003-02-25 7:58 ` jeff
2003-02-25 8:03 ` Thiemo Seufer
2003-02-25 8:17 ` jeff
2003-02-25 8:17 ` jeff
2003-02-25 8:33 ` Thiemo Seufer
2003-02-25 8:46 ` jeff
2003-02-25 8:46 ` jeff
2003-02-25 9:42 ` Thiemo Seufer
2003-02-25 17:47 ` Jun Sun
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=20040113155128.GM14031@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=guardian@killamail.com \
/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.