public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Nottingham <notting@redhat.com>
To: Anders Karlsson <anders@trudheim.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: rebased cpufreq patch?
Date: Mon, 7 Jul 2003 14:36:36 -0400	[thread overview]
Message-ID: <20030707143636.B19538@devserv.devel.redhat.com> (raw)
In-Reply-To: <1057571137.2584.5.camel@tor.trudheim.com>; from anders@trudheim.com on Mon, Jul 07, 2003 at 10:45:37AM +0100

Anders Karlsson (anders@trudheim.com) said: 
> Is there any chance of getting the CPUFreq patch rebased against
> 2.4.22-pre3 ?
> 
> 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.

I believe it's been integrated into the -ac series; that may be
a better place to get it.

Bill


      reply	other threads:[~2003-07-07 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-07  9:45 rebased cpufreq patch? Anders Karlsson
2003-07-07 18:36 ` Bill Nottingham [this message]

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=20030707143636.B19538@devserv.devel.redhat.com \
    --to=notting@redhat.com \
    --cc=anders@trudheim.com \
    --cc=linux-kernel@vger.kernel.org \
    /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