From: Fam Zheng <famz@redhat.com>
To: Ziyue Yang <skiver.cloud.yzy@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Ziyue Yang <yzylivezh@hotmail.com>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v3] gdbstub.c: fix GDB connection segfault caused by empty machines
Date: Wed, 18 Jan 2017 10:15:29 +0800 [thread overview]
Message-ID: <20170118021529.GC31883@lemon.Home> (raw)
In-Reply-To: <1484702885-11437-1-git-send-email-skiver.cloud.yzy@gmail.com>
On Wed, 01/18 09:28, Ziyue Yang wrote:
> Also some updates from fprintf(stderr, ...) to error_report.
Looks like they belong to a separate patch.
Fam
WARNING: multiple messages have this Message-ID (diff)
From: Fam Zheng <famz@redhat.com>
To: Ziyue Yang <skiver.cloud.yzy@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Ziyue Yang <yzylivezh@hotmail.com>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3] gdbstub.c: fix GDB connection segfault caused by empty machines
Date: Wed, 18 Jan 2017 10:15:29 +0800 [thread overview]
Message-ID: <20170118021529.GC31883@lemon.Home> (raw)
In-Reply-To: <1484702885-11437-1-git-send-email-skiver.cloud.yzy@gmail.com>
On Wed, 01/18 09:28, Ziyue Yang wrote:
> Also some updates from fprintf(stderr, ...) to error_report.
Looks like they belong to a separate patch.
Fam
next prev parent reply other threads:[~2017-01-18 2:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 1:28 [Qemu-trivial] [PATCH v3] gdbstub.c: fix GDB connection segfault caused by empty machines Ziyue Yang
2017-01-18 1:28 ` [Qemu-devel] " Ziyue Yang
2017-01-18 2:15 ` Fam Zheng [this message]
2017-01-18 2:15 ` Fam Zheng
2017-01-18 3:25 ` [Qemu-trivial] " Yang Ziyue
2017-01-18 3:25 ` Yang Ziyue
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=20170118021529.GC31883@lemon.Home \
--to=famz@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=skiver.cloud.yzy@gmail.com \
--cc=thuth@redhat.com \
--cc=yzylivezh@hotmail.com \
/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.