From: Jia Liu <proljc@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 1/2] target-openrisc: Free typename in cpu_class_by_name
Date: Mon, 15 Jul 2013 17:09:18 +0800 [thread overview]
Message-ID: <1373879359-12803-2-git-send-email-proljc@gmail.com> (raw)
In-Reply-To: <1373879359-12803-1-git-send-email-proljc@gmail.com>
Add a g_free into openrisc_cpu_class_by_name to free typename.
Signed-off-by: Jia Liu <proljc@gmail.com>
---
target-openrisc/cpu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/target-openrisc/cpu.c b/target-openrisc/cpu.c
index 6d40f1b..e348df0 100644
--- a/target-openrisc/cpu.c
+++ b/target-openrisc/cpu.c
@@ -99,6 +99,7 @@ static ObjectClass *openrisc_cpu_class_by_name(const char *cpu_model)
typename = g_strdup_printf("%s-" TYPE_OPENRISC_CPU, cpu_model);
oc = object_class_by_name(typename);
+ g_free(typename);
if (oc != NULL && (!object_class_dynamic_cast(oc, TYPE_OPENRISC_CPU) ||
object_class_is_abstract(oc))) {
return NULL;
--
1.7.12.4 (Apple Git-37)
next prev parent reply other threads:[~2013-07-15 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 9:09 [Qemu-devel] [PATCH 0/2] target-openrisc hw/openrisc: Two OpenRISC fix Jia Liu
2013-07-15 9:09 ` Jia Liu [this message]
2013-07-15 9:09 ` [Qemu-devel] [PATCH 2/2] hw/openrisc: Use stderr output instead of qemu_log Jia Liu
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=1373879359-12803-2-git-send-email-proljc@gmail.com \
--to=proljc@gmail.com \
--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).