From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH 0/2] Some small documentation fixes
Date: Thu, 16 Feb 2012 18:03:17 +0100 [thread overview]
Message-ID: <1329411799-4266-1-git-send-email-afaerber@suse.de> (raw)
Hey,
I've taken the liberty of rebasing Anthony's gtk-doc patches to verify the
documentation I'm adding in the CPU series. Here's some warning fixes that
came out of this endeavor.
Two open issues remain:
* Identifier extensions (e.g., #Objects) lead to warnings.
* Some structs are not picked up correctly, such as Object.
Regards,
Andreas
Cc: Anthony Liguori <anthony@codemonkey.ws>
Andreas Färber (2):
qom: Fix typo in Object's documentation
qom: Fix identifiers in documentation
include/qemu/object.h | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
--
1.7.7
next reply other threads:[~2012-02-16 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 17:03 Andreas Färber [this message]
2012-02-16 17:03 ` [Qemu-devel] [PATCH 1/2] qom: Fix typo in Object's documentation Andreas Färber
2012-02-16 17:03 ` [Qemu-devel] [PATCH 2/2] qom: Fix identifiers in documentation Andreas Färber
2012-02-17 18:17 ` [Qemu-devel] [PATCH 0/2] Some small documentation fixes Anthony Liguori
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=1329411799-4266-1-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--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).