From: Gerd Hoffmann <kraxel@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/6] virtio-gpu: scanout limit fixes
Date: Fri, 20 May 2016 13:08:19 +0200 [thread overview]
Message-ID: <1463742499.3526.69.camel@redhat.com> (raw)
In-Reply-To: <CAJ+F1CJ2y8LTXLPnfE_A-vuFBMpVCXej3himTj8hLpvaTcVOCA@mail.gmail.com>
On Fr, 2016-05-20 at 11:52 +0200, Marc-André Lureau wrote:
> Hi
>
> On Fri, May 20, 2016 at 7:44 AM, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > On Do, 2016-05-19 at 12:25 +0200, marcandre.lureau@redhat.com wrote:
> >> Here is a small series improving a bit the scanout limit handling. The
> >> first patch was sent previously but is also included in this series
> >> for convenience.
> >
> > Doesn't apply cleanly to master, does this depend on unmerged patches?
> >
>
> No, it was based on 8ec4fe0a4b. There is a small header conflict in
> the third patch that can be trivially solved.
Thanks. Applied against 8ec4fe0a4b & rebased -- in ui queue now.
cheers,
Gerd
prev parent reply other threads:[~2016-05-20 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 10:25 [Qemu-devel] [PATCH 0/6] virtio-gpu: scanout limit fixes marcandre.lureau
2016-05-19 10:25 ` [Qemu-devel] [PATCH 1/6] virtio-gpu: check early scanout id marcandre.lureau
2016-05-19 10:25 ` [Qemu-devel] [PATCH 2/6] virtio-vga: propagate on gpu realized error marcandre.lureau
2016-05-19 10:25 ` [Qemu-devel] [PATCH 3/6] virtio-gpu: check max_outputs value marcandre.lureau
2016-05-19 10:25 ` [Qemu-devel] [PATCH 4/6] virtio-gpu: check max_outputs only marcandre.lureau
2016-05-19 10:25 ` [Qemu-devel] [PATCH 5/6] virtio-gpu: use VIRTIO_GPU_MAX_SCANOUTS marcandre.lureau
2016-05-19 10:26 ` [Qemu-devel] [PATCH 6/6] virtio-gpu: fix ui idx check marcandre.lureau
2016-05-20 5:44 ` [Qemu-devel] [PATCH 0/6] virtio-gpu: scanout limit fixes Gerd Hoffmann
2016-05-20 9:52 ` Marc-André Lureau
2016-05-20 11:08 ` Gerd Hoffmann [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=1463742499.3526.69.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.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 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.