From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Glauber Costa <glommer@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: kvm-userspace: VGA/VESA framebuffer broken
Date: Fri, 05 Dec 2008 17:42:49 +0200 [thread overview]
Message-ID: <49394BF9.6020504@redhat.com> (raw)
In-Reply-To: <4939044B.8080603@siemens.com>
Jan Kiszka wrote:
> That's good. If you want me to test as well, just throw something over.
>
>
It's pushed as tag kvm-80rc3 on kernel.org (will push as master once it
passes the regression tests). Thanks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-12-05 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 10:04 kvm-userspace: VGA/VESA framebuffer broken Jan Kiszka
2008-12-05 10:18 ` Glauber Costa
2008-12-05 10:19 ` Avi Kivity
2008-12-05 10:36 ` Jan Kiszka
2008-12-05 15:42 ` Avi Kivity [this message]
2008-12-05 18:00 ` Jan Kiszka
2008-12-05 18:05 ` Avi Kivity
2008-12-05 18:22 ` Jan Kiszka
2008-12-07 15:01 ` Avi Kivity
2008-12-07 22:20 ` Michael Tokarev
2008-12-08 8:00 ` Jan Kiszka
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=49394BF9.6020504@redhat.com \
--to=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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).