All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	cpufreq list <cpufreq@www.linux.org.uk>
Subject: [PATCH] (resend) support for 900MHz Pentium M for speedstep-centrino.c
Date: 20 Jul 2003 12:16:45 -0700	[thread overview]
Message-ID: <1058728605.5980.41.camel@localhost.localdomain> (raw)

The 900MHz Pentium M has two spaces before the frequency:
"Intel(R) Pentium(R) M processor  900MHz"

This patch adds a 2nd CPU macro (_CPU) which also takes the
stringified speed so that extra spacing can be added.

	J

 i386/kernel/cpu/cpufreq/speedstep-centrino.c |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diff -puN
arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c~centrino-900MHz
arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c
---
local-2.5/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c~centrino-900MHz	2003-07-12 16:38:45.000000000 -0700
+++
local-2.5-jeremy/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c	2003-07-13 00:37:31.000000000 -0700
@@ -156,14 +156,15 @@ static struct cpufreq_frequency_table op
 };
 #undef OP
 
-#define CPU(max)	\
-	{ "Intel(R) Pentium(R) M processor " #max "MHz", (max)*1000, op_##max
}
+#define _CPU(max, name)	\
+	{ "Intel(R) Pentium(R) M processor " name "MHz", (max)*1000, op_##max
}
+#define CPU(max)	_CPU(max, #max)
 
 /* CPU models, their operating frequency range, and freq/voltage
    operating points */
 static const struct cpu_model models[] = 
 {
-	CPU( 900),
+       _CPU( 900, " 900"),
 	CPU(1100),
 	CPU(1200),
 	CPU(1300),

_



             reply	other threads:[~2003-07-20 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 19:16 Jeremy Fitzhardinge [this message]
2003-07-20 21:34 ` [PATCH] (resend) support for 900MHz Pentium M for speedstep-centrino.c Jeremy Fitzhardinge

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=1058728605.5980.41.camel@localhost.localdomain \
    --to=jeremy@goop.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.