mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ameer Armaly <ameer@bellsouth.net>
To: linux-kernel@vger.kernel.org
Subject: [patch] i386 warning cleanups that work
Date: Sat, 20 May 2006 19:59:17 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0605201957070.3380@sg1> (raw)

Here is a version that works, without the efi stuff that caused all the problems, and which I assumed after making the cpu and apm stuff work would work just as easily; just goes to show the
problems with lazyness.

diff --git a/arch/i386/kernel/apm.c b/arch/i386/kernel/apm.c
index df0e174..fc34cf2 100644
--- a/arch/i386/kernel/apm.c
+++ b/arch/i386/kernel/apm.c
@@ -1063,7 +1063,7 @@ #if defined(CONFIG_APM_DISPLAY_BLANK) &&

  static int apm_console_blank(int blank)
  {
-	int error, i;
+	int error = 0, i;
  	u_short state;
  	static const u_short dev[3] = { 0x100, 0x1FF, 0x101 };

@@ -1282,7 +1282,7 @@ static void standby(void)
  static apm_event_t get_event(void)
  {
  	int		error;
-	apm_event_t	event;
+	apm_event_t	event = 0;
  	apm_eventinfo_t	info;

  	static int notified;
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 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-20 23:59 Ameer Armaly [this message]
2006-05-21  0:12 ` Dave Jones

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.0605201957070.3380@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®