qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Robert Reif <reif@earthlink.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] hw/sun4m.c make error messages consistent
Date: Sat, 05 Jan 2008 17:32:05 -0500	[thread overview]
Message-ID: <47800565.7080700@earthlink.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 76 bytes --]

 Make these 3 error messages consistent with the other 20 in the same file.

[-- Attachment #2: patch1.diff.txt --]
[-- Type: text/plain, Size: 1137 bytes --]

diff -p -u -r1.79 sun4m.c
--- hw/sun4m.c	1 Jan 2008 20:57:25 -0000	1.79
+++ hw/sun4m.c	5 Jan 2008 22:26:07 -0000
@@ -385,7 +385,7 @@ static void sun4m_hw_init(const struct h
     for(i = 0; i < smp_cpus; i++) {
         env = cpu_init(cpu_model);
         if (!env) {
-            fprintf(stderr, "Unable to find Sparc CPU definition\n");
+            fprintf(stderr, "qemu: Unable to find Sparc CPU definition\n");
             exit(1);
         }
         cpu_sparc_set_id(env, i);
@@ -554,7 +554,7 @@ static void sun4c_hw_init(const struct h
 
     env = cpu_init(cpu_model);
     if (!env) {
-        fprintf(stderr, "Unable to find Sparc CPU definition\n");
+        fprintf(stderr, "qemu: Unable to find Sparc CPU definition\n");
         exit(1);
     }
 
@@ -1041,7 +1041,7 @@ static void sun4d_hw_init(const struct s
     for (i = 0; i < smp_cpus; i++) {
         env = cpu_init(cpu_model);
         if (!env) {
-            fprintf(stderr, "Unable to find Sparc CPU definition\n");
+            fprintf(stderr, "qemu: Unable to find Sparc CPU definition\n");
             exit(1);
         }
         cpu_sparc_set_id(env, i);

                 reply	other threads:[~2008-01-05 22:32 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=47800565.7080700@earthlink.net \
    --to=reif@earthlink.net \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).