From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH 0/3] virtio-gpu: scanout tracking fixes.
Date: Mon, 2 Jul 2018 18:24:40 +0200 [thread overview]
Message-ID: <20180702162443.16796-1-kraxel@redhat.com> (raw)
Gerd Hoffmann (3):
virtio-gpu: tweak scanout disable.
virtio-gpu: update old resource too.
virtio-gpu: disable scanout when backing resource is destroyed
hw/display/virtio-gpu.c | 64 ++++++++++++++++++++++++++++++++++---------------
1 file changed, 45 insertions(+), 19 deletions(-)
--
2.9.3
next reply other threads:[~2018-07-02 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 16:24 Gerd Hoffmann [this message]
2018-07-02 16:24 ` [Qemu-devel] [PATCH 1/3] virtio-gpu: tweak scanout disable Gerd Hoffmann
2018-07-02 16:24 ` [Qemu-devel] [PATCH 2/3] virtio-gpu: update old resource too Gerd Hoffmann
2018-07-02 16:24 ` [Qemu-devel] [PATCH 3/3] virtio-gpu: disable scanout when backing resource is destroyed Gerd Hoffmann
2018-07-02 16:57 ` [Qemu-devel] [PATCH 0/3] virtio-gpu: scanout tracking fixes Marc-André Lureau
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=20180702162443.16796-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=mst@redhat.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).