From: "Hervé Poussineau" <hpoussin@reactos.org>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>
Subject: [Qemu-devel] [PATCH 1/2] qom: add missing 'const' in documentation sample
Date: Thu, 2 Aug 2012 10:40:29 +0200 [thread overview]
Message-ID: <1343896830-3503-1-git-send-email-hpoussin@reactos.org> (raw)
Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
---
include/qemu/object.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/qemu/object.h b/include/qemu/object.h
index 8b17776..e0d326f 100644
--- a/include/qemu/object.h
+++ b/include/qemu/object.h
@@ -65,7 +65,7 @@ typedef struct InterfaceInfo InterfaceInfo;
* int reg0, reg1, reg2;
* } MyDevice;
*
- * static TypeInfo my_device_info = {
+ * static const TypeInfo my_device_info = {
* .name = TYPE_MY_DEVICE,
* .parent = TYPE_DEVICE,
* .instance_size = sizeof(MyDevice),
--
1.7.10.4
next reply other threads:[~2012-08-02 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 8:40 Hervé Poussineau [this message]
2012-08-02 8:40 ` [Qemu-devel] [PATCH 2/2] esp: add missing const on TypeInfo structures Hervé Poussineau
2012-08-02 15:23 ` Andreas Färber
2012-08-02 15:54 ` Paolo Bonzini
2012-08-02 15:22 ` [Qemu-devel] [PATCH 1/2] qom: add missing 'const' in documentation sample Andreas Färber
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=1343896830-3503-1-git-send-email-hpoussin@reactos.org \
--to=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).