cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: John Clemens <john@deater.net>
Cc: davej@codemonkey.org.uk, cpufreq@www.linux.org.uk
Subject: Re: powernow-k7, something broke in -test3?
Date: Sat, 16 Aug 2003 14:59:22 +0100	[thread overview]
Message-ID: <20030816135922.GQ22433@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0308160115110.27055-100000@pianoman.cluster.toy>

On Sat, Aug 16, 2003 at 01:24:58AM -0400, John Clemens wrote:
 > 
 > Hi Dave,
 > 
 > The following patch corrects a minor think-o in your powernow-k7 changes
 > that went into 2.6.0-test3, and was causing the behavior below.  I don't
 > think you meant to cache the cfid value before you actually read it in :)
 > this was causing all speed notifications to think my previous multiplier
 > was fid_codes[0] (11.0x), and thus screws up loops_per_jiffy, etc..

oh boy, how dumb am I.
Thanks, applied and pushed for 2.6-test4

		Dave

-- 
 Dave Jones     http://www.codemonkey.org.uk

      reply	other threads:[~2003-08-16 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11  2:09 powernow-k7, something broke in -test3? John Clemens
2003-08-16  5:24 ` John Clemens
2003-08-16 13:59   ` 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=20030816135922.GQ22433@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=john@deater.net \
    /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