cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Dominik Brodowski <linux@brodo.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [PATCH] cpufreq: speedstep-lib, speedstep-ich cleanup
Date: Thu, 26 Jun 2003 02:48:31 +0200	[thread overview]
Message-ID: <20030626024831.A31502@suse.de> (raw)
In-Reply-To: <20030616200415.GA4279@brodo.de>; from linux@brodo.de on Mon, Jun 16, 2003 at 10:04:15PM +0200

On Mon, Jun 16, 2003 at 10:04:15PM +0200, Dominik Brodowski wrote:
 > - separate functions which might be useful for speedstep-piix4,
 >   speedstep-via or speedstep-bios into a new speedstep-lib.c.
 > - clean up speedstep-ich as it will only be used for ICH-based chipsets
 >   in future.
 > - remove now-obsolete speedstep_coppermine parameter

Thanks, applied to working tree (I'll merge CVS again after I've
merged another batch of patches which I've backlogged whilst moving
house).

        Dave 

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

           reply	other threads:[~2003-06-26  0:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20030616200415.GA4279@brodo.de>]

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=20030626024831.A31502@suse.de \
    --to=davej@suse.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux@brodo.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