From: Eric Blake <eblake@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>, Markus Armbruster <armbru@redhat.com>
Cc: sfeldma@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] rocker: Use g_new() & friends where that makes obvious sense
Date: Mon, 14 Sep 2015 09:55:40 -0600 [thread overview]
Message-ID: <55F6EDFC.2070503@redhat.com> (raw)
In-Reply-To: <20150914115736.GA2111@nanopsycho.orion>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
On 09/14/2015 05:57 AM, Jiri Pirko wrote:
> Mon, Sep 14, 2015 at 01:52:23PM CEST, armbru@redhat.com wrote:
>> 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.
>
> ^ typo :)
>
This typo is copy-pasted into ALL of your recent g_new() cleanups. Since
you did scattershot threads across multiple maintainers rather than one
big thread, it may be a bit harder to plug all the instances before they
get pulled through the various trees.
>
> Other than that:
>
> Acked-by: Jiri Pirko <jiri@resnulli.us>
Reviewed-by: Eric Blake <eblake@redhat.com>
[In qemu, we tend to use 'Reviewed-by' for "I've inspected the code and
agree it correctly does what the commit message claims", and the weaker
'Acked-by' for "I agree with the fix as documented in the commit message
but didn't inspect the code to ensure that they match"]
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-09-14 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 11:52 [Qemu-devel] [PATCH] rocker: Use g_new() & friends where that makes obvious sense Markus Armbruster
2015-09-14 11:57 ` Jiri Pirko
2015-09-14 15:55 ` Eric Blake [this message]
2015-09-14 16:09 ` Eric Blake
2015-09-14 16:11 ` Markus Armbruster
2015-09-14 19:40 ` Jiri Pirko
2015-09-24 16:18 ` [Qemu-trivial] " Markus Armbruster
2015-09-24 16:18 ` [Qemu-devel] " Markus Armbruster
2015-09-24 18:48 ` [Qemu-trivial] " Jiri Pirko
2015-09-24 18:48 ` [Qemu-devel] " Jiri Pirko
2015-10-03 17:05 ` [Qemu-trivial] " Michael Tokarev
2015-10-03 17:05 ` [Qemu-devel] " 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=55F6EDFC.2070503@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=jiri@resnulli.us \
--cc=qemu-devel@nongnu.org \
--cc=sfeldma@gmail.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 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.