From: "Justin M. Forbes" <jmforbes@linuxtx.org>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0.14] linux-user fixes
Date: Mon, 14 Feb 2011 12:14:58 -0600 [thread overview]
Message-ID: <20110214181458.GA6496@linuxtx.org> (raw)
In-Reply-To: <20110210095310.GA5151@afflict.kos.to>
On Thu, Feb 10, 2011 at 11:53:10AM +0200, Riku Voipio wrote:
> The following changes since commit 343c1de916b1841cd5fd5f813add9c87590d72e8:
>
> x86: Fix MCA broadcast parameters for TCG case (2011-02-08 12:37:30 +0100)
>
> are available in the git repository at:
> git://gitorious.org/qemu-maemo/qemu.git linux-user-for-0.14
>
> Martin Mohring (1):
> linux-user: fix for loopmount ioctl
>
> Stefan Weil (1):
> linux-user: Fix possible realloc memory leak
>
> linux-user/elfload.c | 8 +++++---
> linux-user/ioctls.h | 2 --
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
Applied.
Thanks,
Justin
prev parent reply other threads:[~2011-02-14 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 9:53 [Qemu-devel] [PULL 0.14] linux-user fixes Riku Voipio
2011-02-14 18:14 ` Justin M. Forbes [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=20110214181458.GA6496@linuxtx.org \
--to=jmforbes@linuxtx.org \
--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 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).