From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix dr register typo
Date: Tue, 02 Dec 2008 13:40:35 -0600 [thread overview]
Message-ID: <49358F33.7030403@codemonkey.ws> (raw)
In-Reply-To: <492F2F3C.3090005@web.de>
Jan Kiszka wrote:
> Jan Kiszka wrote:
>
>> ...
>> That reminds me that we should have a "zero new warnings policy" for
>> changes. But reality still looks different...
>>
>
> ...and I'm the first one to shoot (I should really start building also
> upstream qemu with gcc4):
>
> --------->
>
> Fix register name typo in dumping debug registers.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
>
Applied. Thanks.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-12-02 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 21:30 [Qemu-devel] typo in target-i386/ops_sse.h Frank Mehnert
2008-11-27 22:49 ` andrzej zaborowski
2008-11-27 23:13 ` [Qemu-devel] " Jan Kiszka
2008-11-27 23:37 ` [Qemu-devel] [PATCH] fix dr register typo (was: typo in target-i386/ops_sse.h) Jan Kiszka
2008-12-02 19:40 ` Anthony Liguori [this message]
2008-11-28 0:05 ` [Qemu-devel] Re: typo in target-i386/ops_sse.h andrzej zaborowski
2008-11-28 8:23 ` Jan Kiszka
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=49358F33.7030403@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).