From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: "Stefan Weil" <sw@weilnetz.de>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PULL 1.0 0/1] 'info mtree' fix
Date: Sun, 13 Nov 2011 11:48:13 -0600 [thread overview]
Message-ID: <4EC002DD.2040001@codemonkey.ws> (raw)
In-Reply-To: <4EBF9721.9000602@redhat.com>
On 11/13/2011 04:08 AM, Avi Kivity wrote:
> On 11/13/2011 12:06 PM, Avi Kivity wrote:
>> Fix a segfault due to incorrect usage of QTAILQ_FOREACH_SAFE().
>>
>> Avi Kivity (1):
>> memory: fix 'info mtree' segfaults
>>
>> memory.c | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>
>
> Gaaah. If it isn't generated by git request-pull, it's broken.
>
> Please pull from:
>
> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/urgent
>
> to receive the fix above.
Pulled. Thanks.
Regards,
Anthony Liguori
>
prev parent reply other threads:[~2011-11-13 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 10:06 [Qemu-devel] [PULL 1.0 0/1] 'info mtree' fix Avi Kivity
2011-11-13 10:06 ` [Qemu-devel] [PATCH 1.0 1/1] memory: fix 'info mtree' segfaults Avi Kivity
2011-11-13 10:08 ` [Qemu-devel] [PULL 1.0 0/1] 'info mtree' fix Avi Kivity
2011-11-13 17:48 ` Anthony Liguori [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=4EC002DD.2040001@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.