From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qom: Unify type registration
Date: Thu, 09 Feb 2012 11:47:16 -0600 [thread overview]
Message-ID: <4F3406A4.5020800@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA__5XKkG_dR+1-S77cCnLsG0cpD69AU4LvpQ2LjrS+LKQ@mail.gmail.com>
On 02/09/2012 10:49 AM, Peter Maydell wrote:
> On 9 February 2012 14:20, Andreas Färber<afaerber@suse.de> 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.
>
> Ugh, touching the whole tree again?
Yeah, it's not coming from me at least :-)
I doubt this will cause any rebase problems though.
Regards,
Anthony Liguori
>
> -- PMM
>
next prev parent reply other threads:[~2012-02-09 17:47 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
2012-02-09 16:49 ` Peter Maydell
2012-02-09 17:47 ` Anthony Liguori [this message]
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=4F3406A4.5020800@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=peter.maydell@linaro.org \
--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).