From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH RESEND 0/2] Fix leaks on object_property_add_str() setters
Date: Sun, 24 Aug 2014 13:16:07 +0200 [thread overview]
Message-ID: <20140824111607.GD9561@redhat.com> (raw)
In-Reply-To: <20140822193524.GC12310@thinpad.lan.raisama.net>
Are these appropriate for 2.1.1?
Add Cc stable?
On Fri, Aug 22, 2014 at 04:35:24PM -0300, Eduardo Habkost wrote:
> Ping? Who can apply these?
>
> On Wed, Aug 06, 2014 at 03:18:19PM -0300, Eduardo Habkost wrote:
> > Resending two patches from the previous series which were not applied yet.
> >
> >
> > Eduardo Habkost (2):
> > rng-egd: Free old chr_name value before setting new one
> > hw/machine: Free old values of string properties
> >
> > backends/rng-egd.c | 1 +
> > hw/core/machine.c | 8 ++++++++
> > 2 files changed, 9 insertions(+)
> >
> > --
> > 1.9.3
> >
> >
>
> --
> Eduardo
next prev parent reply other threads:[~2014-08-24 11:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 18:18 [Qemu-devel] [PATCH RESEND 0/2] Fix leaks on object_property_add_str() setters Eduardo Habkost
2014-08-06 18:18 ` [Qemu-devel] [PATCH RESEND 1/2] rng-egd: Free old chr_name value before setting new one Eduardo Habkost
2014-08-07 2:24 ` Amos Kong
2014-08-07 10:18 ` Paolo Bonzini
2014-08-25 15:59 ` Amos Kong
2014-08-06 18:18 ` [Qemu-devel] [PATCH RESEND 2/2] hw/machine: Free old values of string properties Eduardo Habkost
2014-08-07 2:24 ` Amos Kong
2014-09-04 15:25 ` Michael S. Tsirkin
2014-08-22 19:35 ` [Qemu-devel] [PATCH RESEND 0/2] Fix leaks on object_property_add_str() setters Eduardo Habkost
2014-08-24 11:16 ` Michael S. Tsirkin [this message]
2014-08-25 11:44 ` Paolo Bonzini
2014-09-04 15:08 ` Eduardo Habkost
2014-09-04 15:29 ` Michael S. Tsirkin
2014-09-04 15:31 ` Michael S. Tsirkin
2014-09-04 15:34 ` Eduardo Habkost
2014-09-04 16:11 ` Michael S. Tsirkin
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=20140824111607.GD9561@redhat.com \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.