From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@amazon.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] Use g_new() & friends where that makes obvious sense
Date: Tue, 04 Feb 2014 18:27:13 +0100 [thread overview]
Message-ID: <52F122F1.5040400@redhat.com> (raw)
In-Reply-To: <877g9aizva.fsf@blackfin.pond.sub.org>
Il 04/02/2014 17:52, Markus Armbruster ha scritto:
> Unfortunately, our use of macros confuses coccinelle sufficiently to
> miss quite a few instances of the patterns. Do we want this change
> anyway?
Yes, we already use g_new anyway.
Paolo
next prev parent reply other threads:[~2014-02-04 17:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 15:53 [Qemu-devel] [PATCH 0/2] Use g_new() & friends where that makes obvious sense Markus Armbruster
2014-01-31 15:53 ` [Qemu-devel] [PATCH 1/2] qga: Fix memory allocation pasto Markus Armbruster
2014-01-31 16:06 ` Eric Blake
2014-01-31 15:53 ` [Qemu-devel] [PATCH 2/2] Use g_new() & friends where that makes obvious sense Markus Armbruster
2014-01-31 17:10 ` Eric Blake
2014-01-31 19:13 ` Richard Henderson
2014-02-03 8:56 ` Markus Armbruster
2014-01-31 16:13 ` [Qemu-devel] [PATCH 0/2] " Peter Maydell
2014-02-03 8:40 ` Markus Armbruster
2014-02-03 9:11 ` Peter Maydell
2014-02-04 16:52 ` Markus Armbruster
2014-02-04 17:27 ` Paolo Bonzini [this message]
2014-02-13 16:36 ` Markus Armbruster
2014-02-13 16:48 ` Peter Maydell
2014-02-13 19:30 ` Markus Armbruster
2014-02-18 15:32 ` Markus Armbruster
2014-02-21 11:10 ` Peter Maydell
2014-02-21 11:49 ` Markus Armbruster
2014-02-21 11:52 ` Peter Maydell
2014-02-21 12:37 ` Markus Armbruster
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=52F122F1.5040400@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--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).