From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Lyude Paul <lyude@redhat.com>,
dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev,
linux-kernel@lists.freedesktop.org
Cc: David Airlie <airlied@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
linux-kernel@vger.kernel.org, Simona Vetter <simona@ffwll.ch>,
Gerd Hoffmann <kraxel@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maxime Ripard <mripard@kernel.org>,
Christian Hergert <christian@sourceandstack.com>
Subject: Re: [PATCH 0/2] drm/virtio: Damage clip fixes
Date: Mon, 7 Sep 2026 15:45:27 +0300 [thread overview]
Message-ID: <3e8af343-404f-44a1-b97c-efbb206ba051@collabora.com> (raw)
In-Reply-To: <20260903211914.1109100-1-lyude@redhat.com>
On 9/4/26 00:15, Lyude Paul wrote:
> A previous associate of mine asked if someone would be able to help with
> upstreaming some work that they had done recently for virtio, and I was
> more then happy to help. These fixes help maintain FB damage clips
> between framebuffer changes, which were previously discarded even when
> userspace provided accumulated per-buffer damage.
>
> Patches apply on top of drm-misc/drm-misc-next.
>
> Christian Hergert (2):
> drm/virtio: preserve damage clips for rendered resources
> drm/virtio: Recalculate ignore_damage_clips on every update
>
> drivers/gpu/drm/virtio/virtgpu_plane.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
>
> base-commit: f9c2f70ee41544717b3c209083073db1e21f919b
Looks okay. Will merge after testing.
--
Best regards,
Dmitry
prev parent reply other threads:[~2026-09-07 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 21:15 [PATCH 0/2] drm/virtio: Damage clip fixes Lyude Paul
2026-09-03 21:15 ` [PATCH 1/2] drm/virtio: preserve damage clips for rendered resources Lyude Paul
2026-09-03 21:15 ` [PATCH 2/2] drm/virtio: Recalculate ignore_damage_clips on every update Lyude Paul
2026-09-07 12:45 ` Dmitry Osipenko [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=3e8af343-404f-44a1-b97c-efbb206ba051@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=airlied@redhat.com \
--cc=christian@sourceandstack.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
/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