cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@arm.linux.org.uk>
To: cpufreq@lists.arm.linux.org.uk
Subject: cpufreq/linux/arch/i386/kernel/cpufreq speedstep-ich.c, 1.5, 1.6 speedstep-piix4.c, 1.9, 1.10
Date: Wed, 03 Sep 2003 08:42:34 +0100	[thread overview]
Message-ID: <E19uSHi-0004jV-MD@flint.arm.linux.org.uk> (raw)

Update of /mnt/src/cvsroot/cpufreq/linux/arch/i386/kernel/cpufreq
In directory flint:/tmp/cvs-serv18189/linux/arch/i386/kernel/cpufreq

Modified Files:
	speedstep-ich.c speedstep-piix4.c 
Log Message:
give correct name to the driver

Index: speedstep-ich.c
===================================================================
RCS file: /mnt/src/cvsroot/cpufreq/linux/arch/i386/kernel/cpufreq/speedstep-ich.c,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- speedstep-ich.c	19 Aug 2003 13:38:32 -0000	1.5
+++ speedstep-ich.c	3 Sep 2003 07:42:31 -0000	1.6
@@ -309,7 +309,7 @@
 
 
 static struct cpufreq_driver speedstep_driver = {
-	.name		= "speedstep",
+	.name		= "speedstep-ich",
 	.verify 	= speedstep_verify,
 	.target 	= speedstep_target,
 	.init		= speedstep_cpu_init,

Index: speedstep-piix4.c
===================================================================
RCS file: /mnt/src/cvsroot/cpufreq/linux/arch/i386/kernel/cpufreq/speedstep-piix4.c,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- speedstep-piix4.c	19 Aug 2003 13:44:59 -0000	1.9
+++ speedstep-piix4.c	3 Sep 2003 07:42:31 -0000	1.10
@@ -281,7 +281,7 @@
 
 
 static struct cpufreq_driver speedstep_driver = {
-	.name		= "speedstep",
+	.name		= "speedstep-piix4",
 	.verify 	= speedstep_verify,
 	.target 	= speedstep_target,
 	.init		= speedstep_cpu_init,

                 reply	other threads:[~2003-09-03  7:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E19uSHi-0004jV-MD@flint.arm.linux.org.uk \
    --to=ducrot@arm.linux.org.uk \
    --cc=cpufreq@lists.arm.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