cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: Bas Mevissen <ml@basmevissen.nl>
Cc: Bas Mevissen <sgm@basmevissen.nl>, Cpufreq@www.linux.org.uk
Subject: Re: Cpufreq for 2.4: what is the best source?
Date: Mon, 18 Aug 2003 19:53:57 +0200	[thread overview]
Message-ID: <20030818175357.GC1570@brodo.de> (raw)
In-Reply-To: <3F409E54.20001@basmevissen.nl>

On Mon, Aug 18, 2003 at 11:37:24AM +0200, Bas Mevissen wrote:
> Dominik Brodowski wrote:
> 
> >
> >Either 2.4.22-rc2-ac1 or the latest 2.4 backport on www.codemonkey.org.uk -
> >but as that's offline at the moment, I'd try -ac. Or 2.6.0-test3-bk-current
> >:)
> >
> 
> Can someone please make a backport of CPUFREQ to 2.4.22-rc2? The -ac has 
>   a new scheduler (backport from 2.6?) and that breaks swsusp for the 
> moment. So I would like to go for 2.4.22-rc2 (or later) with the -ac 
> patches.
> 
> It seems that more people are waiting for a 2.4.22+swsusp+cpufreq, so it 
> is not a waste of time.

Already done. As Dave's site isn't yet back online, it can temporarily be
accessed at
http://www.brodo.de/cpufreq_tmp/cpufreq-2.4.22-rc2-1__.gz

	Dominik

  reply	other threads:[~2003-08-18 17:53 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
2003-08-15 19:40     ` Dominik Brodowski
2003-08-18  9:37   ` Bas Mevissen
2003-08-18 17:53     ` Dominik Brodowski [this message]
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=20030818175357.GC1570@brodo.de \
    --to=linux@brodo.de \
    --cc=Cpufreq@www.linux.org.uk \
    --cc=ml@basmevissen.nl \
    --cc=sgm@basmevissen.nl \
    /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