All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Georg Sauthoff <g_sauthoff@web.de>
Cc: Cpufreq@www.linux.org.uk
Subject: Re: Cpufreq for 2.4: what is the best source?
Date: Fri, 15 Aug 2003 18:39:04 +0100	[thread overview]
Message-ID: <20030815183904.D21529@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200308151853.30238.g_sauthoff@web.de>; from g_sauthoff@web.de on Fri, Aug 15, 2003 at 06:53:30PM +0200

On Fri, Aug 15, 2003 at 06:53:30PM +0200, Georg Sauthoff wrote:
> unfortunely I can't use -ac 2.4. Kernels ... (because of my hardware and not 
> 2.6. because of a Cisco VPN). Is (or was) www.codemonkey.org.uk really the 
> only place, to get the cpufreq backports against vanilla 2.4. kernels?
> 
> What about cvs? And the ftp location mentioned by Bas Mevissen is outdated?

The ftp is updated each night.  Whether it contains anything useful
depends on whether people check the changes into the cvs tree(s).

If people want a 2.4-ac snapshot and the maintainers are willing to
create a cvs branch for them, its pretty simple to add it to nightly
scripts.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

  reply	other threads:[~2003-08-15 17:39 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 [this message]
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

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=20030815183904.D21529@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=Cpufreq@www.linux.org.uk \
    --cc=g_sauthoff@web.de \
    /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.