cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: cpufreq@www.linux.org.uk
Subject: Re: [PATCHES] cpufreq_get(), cpufreq->get()
Date: Wed, 14 Apr 2004 11:52:52 +0100	[thread overview]
Message-ID: <20040414105250.GE24970@redhat.com> (raw)
In-Reply-To: <20040411215912.GA8160@dominikbrodowski.de>

On Sun, Apr 11, 2004 at 11:59:12PM +0200, Dominik Brodowski wrote:

 > The following patchset is based on the current cpufreq bitkeeper patch
 > and one important speedstep-centrino patch 
 > [see http://www.linux.org.uk/mailman/private/cpufreq/2004-April/003499.html ].
 > 
 > I suggest that this patchset is considered for the 2.6.7 timeframe; 
 > while the x86 parts seem to be quite straightforward, the arm 
 > architecture might be affected more heavily: it already relied on 
 > cpufreq_get(), and I can't verify my changes do even compile. Russell, 
 > I hope I didn't break anything this time...

Lets roll these in after 2.6.6 is out, and they can sit in -mm for a while.

		Dave

      parent reply	other threads:[~2004-04-14 10:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-11 21:59 [PATCHES] cpufreq_get(), cpufreq->get() Dominik Brodowski
2004-04-11 22:00 ` patch-02 [Re: [PATCHES] cpufreq_get(), cpufreq->get()] Dominik Brodowski
2004-04-11 22:00 ` patch-04 " Dominik Brodowski
2004-04-11 22:00 ` patch-05 " Dominik Brodowski
2004-04-11 22:01 ` patch-06 " Dominik Brodowski
2004-04-12 12:04 ` give the TSC a fair chance [Was: " Dominik Brodowski
2004-04-14 18:24   ` john stultz
2004-04-14 18:54     ` Dominik Brodowski
2004-04-14 20:03       ` john stultz
2004-04-14 20:57         ` Dominik Brodowski
2004-04-14 21:24           ` john stultz
2004-04-19 15:32             ` Dominik Brodowski
2004-04-14 10:52 ` Dave Jones [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=20040414105250.GE24970@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.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