All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: Ralf Baechle <ralf@linux-mips.org>,
	linux mips mailing list <linux-mips@linux-mips.org>
Subject: [PATCH]: read_c0_* return always a long
Date: 19 Dec 2002 12:03:40 +0100	[thread overview]
Message-ID: <m28yyml183.fsf@demo.mitica> (raw)


Hi
        this function returns a long, nuke a call to read_c0_errorepc
        and use right types for variables and printks.

Later, Juan.

Index: arch/mips/kernel/traps.c
===================================================================
RCS file: /home/cvs/linux/arch/mips/kernel/traps.c,v
retrieving revision 1.99.2.38
diff -u -r1.99.2.38 traps.c
--- arch/mips/kernel/traps.c	17 Dec 2002 23:41:01 -0000	1.99.2.38
+++ arch/mips/kernel/traps.c	19 Dec 2002 10:17:47 -0000
@@ -781,14 +781,14 @@
 
 asmlinkage void cache_parity_error(void)
 {
-	unsigned int reg_val;
+	unsigned long reg_val;
 
 	/* For the moment, report the problem and hang. */
 	reg_val = read_c0_errorepc();
 	printk("Cache error exception:\n");
-	printk("cp0_errorepc == %08x\n", read_c0_errorepc());
+	printk("cp0_errorepc == %08lx\n", reg_val);
 	reg_val = read_c0_cacheerr();
-	printk("c0_cacheerr == %08x\n", reg_val);
+	printk("c0_cacheerr == %08lx\n", reg_val);
 
 	printk("Decoded c0_cacheerr: %s cache fault in %s reference.\n",
 	       reg_val & (1<<30) ? "secondary" : "primary",


-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

                 reply	other threads:[~2002-12-19 10:58 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=m28yyml183.fsf@demo.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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.