From: Saurav Sachidanand <sauravsachidanand@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH v4] util: Use g_malloc/g_free in envlist.c
Date: Mon, 20 Mar 2017 17:36:23 +0000 [thread overview]
Message-ID: <CACKq+iXP8eE6XPbTfRTvpsbf1Mks36G5eKasM0Cowi41uj1_5Q@mail.gmail.com> (raw)
In-Reply-To: <20170320173258.3621-1-sauravsachidanand@gmail.com>
On Mon, Mar 20, 2017 at 5:32 PM, Saurav Sachidanand
<sauravsachidanand@gmail.com> wrote:
> Change malloc/strdup/free to g_malloc/g_strdup/g_free in
> util/envlist.c.
>
> Remove NULL checks for pointers returned from g_malloc and g_strdup
> as they exit in case of failure. Also, update calls to envlist_create
> to reflect this.
>
> Free array and array contents returned by envlist_to_environ using
> g_free in bsd-user/main.c and linux-user/main.c.
>
> Update comments to reflect change in semantics.
> ---
Sorry, forgot to sign it.
prev parent reply other threads:[~2017-03-20 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 17:32 [Qemu-devel] [Qemu-trivial] [PATCH v4] util: Use g_malloc/g_free in envlist.c Saurav Sachidanand
2017-03-20 17:36 ` Saurav Sachidanand [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=CACKq+iXP8eE6XPbTfRTvpsbf1Mks36G5eKasM0Cowi41uj1_5Q@mail.gmail.com \
--to=sauravsachidanand@gmail.com \
--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).