From: Markus Armbruster <armbru@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
riku.voipio@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] linux-user: Use g_new() & friends where that makes obvious sense
Date: Thu, 24 Sep 2015 18:19:48 +0200 [thread overview]
Message-ID: <87k2rfbxi3.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <5603A3B4.1020900@weilnetz.de> (Stefan Weil's message of "Thu, 24 Sep 2015 09:18:12 +0200")
Stefan Weil <sw@weilnetz.de> writes:
> Am 24.09.2015 um 09:06 schrieb Markus Armbruster:
>> Ping?
>>
>> Markus Armbruster <armbru@redhat.com> writes:
>>
>>> g_new(T, n) is neater than g_malloc(sizeof(T) * n). It's also
>>> safer, for two reasons. One, it catches multiplication
>>> overflowing size_t. Two, it returns T * rather than void *,
>>> which lets the compiler catch more type errors.
>>>
>>> This commit only touches allocations with size arguments of the
>>> form sizeof(T). Same Coccinelle semantic patchas in commit
>>> b45c03f.
>>>
>>> Signed-off-by: Markus Armbruster <armbru@redhat.com> ---
>>> linux-user/elfload.c | 2 +- linux-user/main.c | 2 +-
>>> linux-user/syscall.c | 2 +- 3 files changed, 3 insertions(+), 3
>>> deletions(-)
>
> Reviewed-by: Stefan Weil <sw@weilnetz.de>
>
> This patch is trivial enough for qemu-trivial.
I guess it is. For code with a maintainer, I tend to try the maintainer
first.
> As Eric has written, the commit message needs
> a small correction: s/patchas/patch as/
Yes.
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
riku.voipio@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: Use g_new() & friends where that makes obvious sense
Date: Thu, 24 Sep 2015 18:19:48 +0200 [thread overview]
Message-ID: <87k2rfbxi3.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <5603A3B4.1020900@weilnetz.de> (Stefan Weil's message of "Thu, 24 Sep 2015 09:18:12 +0200")
Stefan Weil <sw@weilnetz.de> writes:
> Am 24.09.2015 um 09:06 schrieb Markus Armbruster:
>> Ping?
>>
>> Markus Armbruster <armbru@redhat.com> writes:
>>
>>> g_new(T, n) is neater than g_malloc(sizeof(T) * n). It's also
>>> safer, for two reasons. One, it catches multiplication
>>> overflowing size_t. Two, it returns T * rather than void *,
>>> which lets the compiler catch more type errors.
>>>
>>> This commit only touches allocations with size arguments of the
>>> form sizeof(T). Same Coccinelle semantic patchas in commit
>>> b45c03f.
>>>
>>> Signed-off-by: Markus Armbruster <armbru@redhat.com> ---
>>> linux-user/elfload.c | 2 +- linux-user/main.c | 2 +-
>>> linux-user/syscall.c | 2 +- 3 files changed, 3 insertions(+), 3
>>> deletions(-)
>
> Reviewed-by: Stefan Weil <sw@weilnetz.de>
>
> This patch is trivial enough for qemu-trivial.
I guess it is. For code with a maintainer, I tend to try the maintainer
first.
> As Eric has written, the commit message needs
> a small correction: s/patchas/patch as/
Yes.
next prev parent reply other threads:[~2015-09-24 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 11:53 [Qemu-devel] [PATCH] linux-user: Use g_new() & friends where that makes obvious sense Markus Armbruster
2015-09-14 15:51 ` Eric Blake
2015-09-14 16:08 ` Eric Blake
2015-09-24 7:06 ` Markus Armbruster
2015-09-24 7:18 ` [Qemu-trivial] " Stefan Weil
2015-09-24 7:18 ` Stefan Weil
2015-09-24 16:19 ` Markus Armbruster [this message]
2015-09-24 16:19 ` Markus Armbruster
2015-10-03 17:07 ` [Qemu-trivial] " Michael Tokarev
2015-10-03 17:07 ` Michael Tokarev
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=87k2rfbxi3.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=sw@weilnetz.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.