From: Max Reitz <mreitz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block: Use g_new0() for a bit of extra type checking
Date: Thu, 04 Dec 2014 14:03:49 +0100 [thread overview]
Message-ID: <54805BB5.10900@redhat.com> (raw)
In-Reply-To: <1417697709-13087-1-git-send-email-armbru@redhat.com>
On 2014-12-04 at 13:55, Markus Armbruster wrote:
> g_new(T, 1) is safer than g_malloc(sizeof(T)), because it returns T *
> rather than void *, which lets the compiler catch more type errors.
>
> Missed in commit 02c4f26.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> aio-posix.c | 2 +-
> aio-win32.c | 4 ++--
> async.c | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
Thanks, applied to my block-next tree:
https://github.com/XanClic/qemu/commits/block-next
prev parent reply other threads:[~2014-12-04 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 12:55 [Qemu-devel] [PATCH] block: Use g_new0() for a bit of extra type checking Markus Armbruster
2014-12-04 13:03 ` Max Reitz [this message]
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=54805BB5.10900@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).