From: Michael Tokarev <mjt@tls.msk.ru>
To: Alon Levy <alevy@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] libcacard: g_malloc cleanups
Date: Sun, 11 May 2014 15:42:23 +0400 [thread overview]
Message-ID: <536F621F.1010008@msgid.tls.msk.ru> (raw)
In-Reply-To: <536F2EE0.10305@redhat.com>
11.05.2014 12:03, Alon Levy wrote:
[]
>> diff --git a/libcacard/cac.c b/libcacard/cac.c
>> index 74ef3e3..122129e 100644
>> --- a/libcacard/cac.c
>> +++ b/libcacard/cac.c
>> @@ -310,16 +310,11 @@ static VCardAppletPrivate *
>> cac_new_pki_applet_private(const unsigned char *cert,
>> int cert_len, VCardKey *key)
>> {
>> - CACPKIAppletData *pki_applet_data = NULL;
>> - VCardAppletPrivate *applet_private = NULL;
>
> These two lines above (and the corresponding ones beloow) seem unrelated
> to this patch.
>
>> - applet_private = (VCardAppletPrivate *)g_malloc(sizeof(VCardAppletPrivate));
>> + CACPKIAppletData *pki_applet_data;
>> + VCardAppletPrivate *applet_private;
>>
>> + applet_private = g_new0(VCardAppletPrivate, 1);
Yes, that's removal of initial value setting of variables which
will be initialized on the next line. It is like cleaning up
coding style (spacing around {} etc) in a nearby lines. I can
mention this in the commit message, but I don't really think it
is really important.
Thanks,
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Alon Levy <alevy@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] libcacard: g_malloc cleanups
Date: Sun, 11 May 2014 15:42:23 +0400 [thread overview]
Message-ID: <536F621F.1010008@msgid.tls.msk.ru> (raw)
In-Reply-To: <536F2EE0.10305@redhat.com>
11.05.2014 12:03, Alon Levy wrote:
[]
>> diff --git a/libcacard/cac.c b/libcacard/cac.c
>> index 74ef3e3..122129e 100644
>> --- a/libcacard/cac.c
>> +++ b/libcacard/cac.c
>> @@ -310,16 +310,11 @@ static VCardAppletPrivate *
>> cac_new_pki_applet_private(const unsigned char *cert,
>> int cert_len, VCardKey *key)
>> {
>> - CACPKIAppletData *pki_applet_data = NULL;
>> - VCardAppletPrivate *applet_private = NULL;
>
> These two lines above (and the corresponding ones beloow) seem unrelated
> to this patch.
>
>> - applet_private = (VCardAppletPrivate *)g_malloc(sizeof(VCardAppletPrivate));
>> + CACPKIAppletData *pki_applet_data;
>> + VCardAppletPrivate *applet_private;
>>
>> + applet_private = g_new0(VCardAppletPrivate, 1);
Yes, that's removal of initial value setting of variables which
will be initialized on the next line. It is like cleaning up
coding style (spacing around {} etc) in a nearby lines. I can
mention this in the commit message, but I don't really think it
is really important.
Thanks,
/mjt
next prev parent reply other threads:[~2014-05-11 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 15:54 [Qemu-trivial] [PATCH] libcacard: g_malloc cleanups Michael Tokarev
2014-05-08 15:54 ` [Qemu-devel] " Michael Tokarev
2014-05-11 8:03 ` [Qemu-trivial] " Alon Levy
2014-05-11 8:03 ` Alon Levy
2014-05-11 11:42 ` Michael Tokarev [this message]
2014-05-11 11:42 ` Michael Tokarev
2014-05-17 7:49 ` [Qemu-trivial] " Michael Tokarev
2014-05-17 7:49 ` [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=536F621F.1010008@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=alevy@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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.