From: Ameer Armaly <ameer@bellsouth.net>
To: linux-kernel@vger.kernel.org
Subject: [patch] intialize cpu_freq in arch/i386/kernel/cpu/transmeta.c
Date: Sat, 20 May 2006 16:50:59 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0605201648430.18009@sg1> (raw)
Initializing cpu_freq to 0 in arch/i386/kernel/cpu/transmeta.c gets rid of
an unnecessary warning.
Initialized cpu_freq in arch/i386/kernel/cpu/transmeta.c to suppress warning.
---
commit 53121ea5e13e075e5239734bb26c3cae7ee84ee0
tree 0eca3170380c610969118c6fa7700558b7232e5d
parent 6566a3f8f3281497a81815dfe2b64eb54dafe05d
author Ameer Armaly <ameer_armaly@hotmail.com> Sat, 20 May 2006 16:43:05 -0400
committer Ameer Armaly <ameer@sg1.(none)> Sat, 20 May 2006 16:43:05 -0400
arch/i386/kernel/cpu/transmeta.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/i386/kernel/cpu/transmeta.c b/arch/i386/kernel/cpu/transmeta.c
index 7214c9b..0737890 100644
--- a/arch/i386/kernel/cpu/transmeta.c
+++ b/arch/i386/kernel/cpu/transmeta.c
@@ -9,7 +9,7 @@ static void __init init_transmeta(struct
{
unsigned int cap_mask, uk, max, dummy;
unsigned int cms_rev1, cms_rev2;
- unsigned int cpu_rev, cpu_freq, cpu_flags, new_cpu_rev;
+ unsigned int cpu_rev, cpu_freq = 0, cpu_flags, new_cpu_rev;
char cpu_info[65];
get_model_name(c); /* Same as AMD/Cyrix */
reply other threads:[~2006-05-20 20:51 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=Pine.LNX.4.61.0605201648430.18009@sg1 \
--to=ameer@bellsouth.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®