From: Anthony Liguori <anthony@codemonkey.ws>
To: riku voipio <riku.voipio@iki.fi>
Cc: aliguori@us.ibm.com, Laurent Vivier <Laurent@Vivier.EU>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PING 0.14] Missing patches (mostly fixes)
Date: Mon, 07 Feb 2011 07:09:31 -0600 [thread overview]
Message-ID: <4D4FEF0B.3080502@codemonkey.ws> (raw)
In-Reply-To: <4D4DA7C9.3020504@iki.fi>
On 02/05/2011 01:40 PM, riku voipio wrote:
> On 02/03/2011 12:16 PM, Laurent Vivier wrote:
>>> On Wed, Feb 02, 2011 at 08:28:15PM +0100, Stefan Weil wrote:
>>>> [PATCH] linux-user: Fix possible realloc memory leak
>>>> (http://patchwork.ozlabs.org/patch/79217/)
>>> Looks ok for me.
>
>> And this one ?
>>
>> linux-user: correct core dump format
>>
>> http://patchwork.ozlabs.org/patch/78464/
>
> Do you need it for 0.14 ?
>
> I intend to include this and other in a pull request for master soon.
This looks reasonably important. Can you just do a pull request for
master for the patches that might be good for 0.14?
If you can do that in the next couple days, it'll make it into -rc2 no
problem.
Regards,
Anthony Liguori
> Riku
>
next prev parent reply other threads:[~2011-02-07 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 10:16 [Qemu-devel] Re: [PING 0.14] Missing patches (mostly fixes) Laurent Vivier
2011-02-05 19:40 ` riku voipio
2011-02-07 13:09 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-09 10:14 Laurent Vivier
2011-02-09 9:20 Laurent Vivier
2011-02-09 9:52 ` Peter Maydell
2011-02-09 10:25 ` Riku Voipio
2011-02-05 21:49 Laurent Vivier
2011-02-09 7:03 ` Riku Voipio
2011-01-27 8:29 [Qemu-devel] [0.14] Queue of 0.14 patches/pull? Paolo Bonzini
2011-02-02 19:28 ` [Qemu-devel] [PING 0.14] Missing patches (mostly fixes) Stefan Weil
2011-02-02 21:25 ` [Qemu-devel] " Michael S. Tsirkin
2011-02-03 7:00 ` Riku Voipio
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=4D4FEF0B.3080502@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Laurent@Vivier.EU \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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.