qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] sb16 debug output
Date: Mon, 14 Feb 2005 14:40:13 +1300	[thread overview]
Message-ID: <1108345214.1601.34.camel@localhost.localdomain> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 209 bytes --]

Hi,

    Attached is a purely frivolous patch to correct a typo that's slowly
been driving me nuts in the debug output from the sb16 code :)

Cheers,
-- 
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>

[-- Attachment #1.2: Type: text/html, Size: 627 bytes --]

[-- Attachment #2: sb16_truly.patch --]
[-- Type: text/x-patch, Size: 422 bytes --]

diff -ru qemu/hw/sb16.c qemu_truly/hw/sb16.c
--- qemu/hw/sb16.c      2004-11-15 05:02:09.000000000 +1300
+++ qemu_truly/hw/sb16.c        2005-02-14 14:35:00.343493670 +1300
@@ -540,7 +540,7 @@
     return;

  warn:
-    dolog ("warning: command %#x,%d is not trully understood yet\n",
+    dolog ("warning: command %#x,%d is not truly understood yet\n",
            cmd, s->needed_bytes);
     s->cmd = cmd;
     return;


                 reply	other threads:[~2005-02-14  1:57 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=1108345214.1601.34.camel@localhost.localdomain \
    --to=esrever_otua@pythonhacker.is-a-geek.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).