From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH] Fix compiler warning
Date: Sun, 20 Jul 2008 17:17:51 +0200 [thread overview]
Message-ID: <4883571F.1070802@mail.berlios.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
Hello,
this patch fixes a compiler warning (signed/unsigned char mismatch).
There is no reason to use unsigned char * instead of char *.
Please apply it to Qemu SVN trunk.
Regards
Stefan
[-- Attachment #2: mips_translate_init.patch --]
[-- Type: text/x-diff, Size: 570 bytes --]
Index: target-mips/translate_init.c
===================================================================
--- target-mips/translate_init.c (Revision 4908)
+++ target-mips/translate_init.c (Arbeitskopie)
@@ -63,7 +63,7 @@
};
struct mips_def_t {
- const unsigned char *name;
+ const char *name;
int32_t CP0_PRid;
int32_t CP0_Config0;
int32_t CP0_Config1;
@@ -417,7 +417,7 @@
#endif
};
-static const mips_def_t *cpu_mips_find_by_name (const unsigned char *name)
+static const mips_def_t *cpu_mips_find_by_name (const char *name)
{
int i;
reply other threads:[~2008-07-20 15:17 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=4883571F.1070802@mail.berlios.de \
--to=weil@mail.berlios.de \
--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).