cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: anders@trudheim.com
Cc: davej@suse.de, cpufreq@www.linux.org.uk
Subject: Re: rebased cpufreq patch?
Date: Mon, 7 Jul 2003 14:34:48 +0200	[thread overview]
Message-ID: <20030707123448.GA1905@brodo.de> (raw)

> Hi there,
> 
> Is there any chance of getting the CPUFreq patch rebased against
> 2.4.22-pre3 ?

I'll be working on an updated version within the next few days, check
http://www.codemonkey.org.uk/cpufreq/ for updated patches, please.

> I have been using the two patches linux-2.4.20-cpufreq.patch and
> cpufreq-centrino.patch against 2.4.21-rc7-ac1 since June 12th without
> any problems. From what I can tell, it is working very well indeed, so
> if it could be included in -pre4 it'd be great.

IMHO it's no stuff for 2.4.22. Davej/Russell, what's your opinion about 2.4.
in general?

	Dominik

             reply	other threads:[~2003-07-07 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-07 12:34 Dominik Brodowski [this message]
2003-07-07 17:38 ` rebased cpufreq patch? Dave Jones
2003-07-07 18:38   ` Benjamin Herrenschmidt

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=20030707123448.GA1905@brodo.de \
    --to=linux@brodo.de \
    --cc=anders@trudheim.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox