From: malc <av1474@comtv.ru>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qom: Unify type registration
Date: Thu, 9 Feb 2012 20:41:40 +0400 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1202092040570.1519@linmac> (raw)
In-Reply-To: <1328797255-18410-1-git-send-email-afaerber@suse.de>
On Thu, 9 Feb 2012, Andreas F?rber wrote:
> Replace device_init() with generalized type_init().
>
> While at it, unify naming convention: type_init([$prefix_]register_types)
> Also, type_init() is a function, so add preceding blank line where
> necessary and don't put a semicolon after the closing brace.
>
> Signed-off-by: Andreas F?rber <afaerber@suse.de>
> Cc: Anthony Liguori <anthony@codemonkey.ws>
> Cc: malc <av1474@comtv.ru>
No objectsions, thanks for the effort.
[..snip..]
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2012-02-09 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 14:20 [Qemu-devel] [PATCH v2] qom: Unify type registration Andreas Färber
2012-02-09 16:41 ` malc [this message]
2012-02-09 16:49 ` Peter Maydell
2012-02-09 17:47 ` Anthony Liguori
2012-02-10 22:38 ` 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=alpine.LNX.2.00.1202092040570.1519@linmac \
--to=av1474@comtv.ru \
--cc=afaerber@suse.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).