public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Michael Clark <michael@metaparadigm.com>
Cc: jeremy@goop.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] - Initial dothan speedstep support
Date: Mon, 9 Aug 2004 15:28:19 +0100	[thread overview]
Message-ID: <20040809142819.GD21238@redhat.com> (raw)
In-Reply-To: <411365C9.5020909@metaparadigm.com>

On Fri, Aug 06, 2004 at 07:04:41PM +0800, Michael Clark wrote:
 > On 08/06/04 13:03, Michael Clark wrote:
 > >Hi All,
 > >
 > >Was looking for a patch for Dothan cpufreq support but could only
 > >find the stepping identification code here:
 > >
 > >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm6/broken-out/bk-cpufreq.patch 
 > 
 > I've since found there is a newer speedstep-centrino in 2.6.8-rc3-mm1
 > although still without dothan support but slight changes for more
 > informative messages about steppings without needed table support.
 > 
 > So i've rediffed table support for dothan b0 steppings to 2.6.8-rc3-mm1

Merged, thanks.
I've accumulated quite a lot of changes in the cpufreq bk tree
(around 30 csets), and Linus didn't respond the last time I asked
him to merge, so it may be he feels theres too much change
for an RC -> Final transition.  I'll send a pull request again
when 2.6.9 opens up.

		Dave


  reply	other threads:[~2004-08-09 14:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06  5:03 [PATCH] - Initial dothan speedstep support Michael Clark
2004-08-06 11:04 ` Michael Clark
2004-08-09 14:28   ` Dave Jones [this message]
2004-08-10 11:59     ` Michael Clark
2004-08-10 12:16       ` Michael Clark
2004-08-18 13:53 ` Pavel Machek
2004-08-22  7:31   ` Clark, Michael
2004-08-23  0:33     ` Michael Clark

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=20040809142819.GD21238@redhat.com \
    --to=davej@redhat.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@metaparadigm.com \
    /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