From: Javier Martinez Canillas <javierm@redhat.com>
To: Zack Rusin <zackr@vmware.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"olvaffe@gmail.com" <olvaffe@gmail.com>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"nunes.erico@gmail.com" <nunes.erico@gmail.com>,
"airlied@redhat.com" <airlied@redhat.com>,
"pekka.paalanen@collabora.com" <pekka.paalanen@collabora.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"belmouss@redhat.com" <belmouss@redhat.com>,
"mripard@kernel.org" <mripard@kernel.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"gurchetansingh@chromium.org" <gurchetansingh@chromium.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"kraxel@redhat.com" <kraxel@redhat.com>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
"airlied@gmail.com" <airlied@gmail.com>,
Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>,
"contact@emersion.fr" <contact@emersion.fr>
Subject: Re: [PATCH v2 0/5] drm: Allow the damage helpers to handle buffer damage
Date: Thu, 16 Nov 2023 08:46:14 +0100 [thread overview]
Message-ID: <87o7fu5eex.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <a16a61582f90a5b490fb7681b44864a4801c830a.camel@vmware.com>
Zack Rusin <zackr@vmware.com> writes:
Hello Zack,
> On Wed, 2023-11-15 at 14:15 +0100, Javier Martinez Canillas wrote:
[...]
>>
>> Changes in v2:
>> - Add a struct drm_plane_state .ignore_damage_clips to set in the plane's
>> .atomic_check, instead of having different helpers (Thomas Zimmermann).
>> - Set struct drm_plane_state .ignore_damage_clips in virtio-gpu plane's
>> .atomic_check instead of using a different helpers (Thomas Zimmermann).
>> - Set struct drm_plane_state .ignore_damage_clips in vmwgfx plane's
>> .atomic_check instead of using a different helpers (Thomas Zimmermann).
>
> The series looks good to me, thanks for tackling this. I'm surprised that we don't
Thanks. Can I get your r-b or a-b ?
> have any IGT tests for this. Seems like it shouldn't be too hard to test it in a
> generic way with just a couple of dumb buffers.
>
Yes, I haven't looked at it but also think that shouldn't be that hard.
> z
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2023-11-16 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 13:15 [PATCH v2 0/5] drm: Allow the damage helpers to handle buffer damage Javier Martinez Canillas
2023-11-15 13:15 ` [PATCH v2 5/5] drm/todo: Add entry about implementing buffer age for damage tracking Javier Martinez Canillas
2023-11-16 4:04 ` [PATCH v2 0/5] drm: Allow the damage helpers to handle buffer damage Zack Rusin
2023-11-16 7:46 ` Javier Martinez Canillas [this message]
2023-11-16 12:07 ` Thomas Zimmermann
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=87o7fu5eex.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=Linux-graphics-maintainer@vmware.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=belmouss@redhat.com \
--cc=contact@emersion.fr \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=kraxel@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nunes.erico@gmail.com \
--cc=olvaffe@gmail.com \
--cc=pekka.paalanen@collabora.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
--cc=zackr@vmware.com \
/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