From: Amit Shah <amit.shah@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: borntraeger@de.ibm.com, agraf@suse.de, qemu list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PULL] virtio-serial: Fix console failure on unconnected pty
Date: Tue, 3 Jan 2012 21:18:20 +0530 [thread overview]
Message-ID: <20120103154820.GA4536@amit.redhat.com> (raw)
Hi,
This patch fixes a frozen guest on virtio-console output before a pty
is connected. Please pull.
The following changes since commit 8d3bc5178fbc06cdd89c064ae8f44e77c503e91e:
Fix qapi code generation wrt parallel build (2011-12-27 09:28:58 -0600)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/qemu/amit/char.git ..BRANCH.NOT.VERIFIED..
Christian Borntraeger (1):
virtio-console: Fix failure on unconnected pty
hw/virtio-serial-bus.c | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1 deletions(-)
Amit
next reply other threads:[~2012-01-03 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 15:48 Amit Shah [this message]
2012-01-03 15:50 ` [Qemu-devel] [PULL] virtio-serial: Fix console failure on unconnected pty Amit Shah
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=20120103154820.GA4536@amit.redhat.com \
--to=amit.shah@redhat.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=borntraeger@de.ibm.com \
--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 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).