From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/2] virtio-gpu: coverity fixes
Date: Mon, 18 Nov 2024 11:01:54 +0000 [thread overview]
Message-ID: <87bjycu7od.fsf@draig.linaro.org> (raw)
In-Reply-To: <20241114085241-mutt-send-email-mst@kernel.org> (Michael S. Tsirkin's message of "Thu, 14 Nov 2024 08:52:54 -0500")
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Mon, Nov 11, 2024 at 11:00:38PM +0000, Alex Bennée wrote:
>> v2,
>>
>> Fixes after Dimitry's review.
>
>
> You should CC Gerd.
Since 2f8cd5a9b6 (MAINTAINERS: drop virtio-gpu maintainership)
virtio-gpu is currently orphaned for maintainers. I've been reaching out
to various teams with GPU experience (including Dimitry) to see if we
can find a replacement maintainer. For now I'm happy to test and
upstream odd fixes.
>
>> Alex.
>>
>> Alex Bennée (2):
>> hw/display: factor out the scanout blob to fb conversion
>> hw/display: check frame buffer can hold blob
>>
>> include/hw/virtio/virtio-gpu.h | 15 +++++++++
>> hw/display/virtio-gpu-virgl.c | 22 +------------
>> hw/display/virtio-gpu.c | 59 +++++++++++++++++++++-------------
>> 3 files changed, 52 insertions(+), 44 deletions(-)
>>
>> --
>> 2.39.5
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2024-11-18 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 23:00 [PATCH v2 0/2] virtio-gpu: coverity fixes Alex Bennée
2024-11-11 23:00 ` [PATCH v2 1/2] hw/display: factor out the scanout blob to fb conversion Alex Bennée
2024-11-14 10:00 ` Dmitry Osipenko
2024-11-11 23:00 ` [PATCH v2 2/2] hw/display: check frame buffer can hold blob Alex Bennée
2024-11-14 10:01 ` Dmitry Osipenko
2024-11-14 13:52 ` [PATCH v2 0/2] virtio-gpu: coverity fixes Michael S. Tsirkin
2024-11-18 11:01 ` Alex Bennée [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=87bjycu7od.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--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 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.