cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Mevissen <ml@basmevissen.nl>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Dominik Brodowski <linux@brodo.de>, cpufreq@www.linux.org.uk
Subject: Re: cpufreq and 2.4.
Date: Mon, 18 Aug 2003 14:13:53 +0200	[thread overview]
Message-ID: <3F40C301.1010101@basmevissen.nl> (raw)
In-Reply-To: <20030818115729.A31111@flint.arm.linux.org.uk>

Russell King wrote:

> On Mon, Aug 18, 2003 at 12:47:36PM +0200, Bas Mevissen wrote:

> I don't think so.  PM is still developing in 2.6, and there's a fair
> amount of work that needs to be done in that area.  I'm not aware of
> anyone looking into this topic on "interesting ARM platforms" at
> present - the main focus today continues to be 2.4-based kernels.
> 

OK. What is better for ARM: what is in 2.4 now or a backport of what is 
in 2.6 now? The answer to that question helps Dominik in finding out 
what to do with the ARM stuff when backporting cpufreq from 2.6.

Regards,

Bas.

  reply	other threads:[~2003-08-18 12:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 15:35 cpufreq and 2.4 Dominik Brodowski
2003-08-18  7:39 ` Ducrot Bruno
2003-08-18 10:14   ` Bas Mevissen
2003-08-18 12:49     ` Ducrot Bruno
2003-08-18 13:21       ` Bas Mevissen
2003-08-18 10:47 ` Bas Mevissen
2003-08-18 10:57   ` Russell King
2003-08-18 12:13     ` Bas Mevissen [this message]
2003-08-18 18:10       ` Russell King
2003-08-18 18:00   ` Dominik Brodowski
2003-08-19  7:24     ` Ducrot Bruno
2003-08-19  8:58       ` Bas Mevissen
2003-08-19  8:45     ` Bas Mevissen
2003-08-19 11:42       ` 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=3F40C301.1010101@basmevissen.nl \
    --to=ml@basmevissen.nl \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux@brodo.de \
    --cc=rmk@arm.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