From: "Maaz Mombasawala <maaz.mombasawala@broadcom.com>" <maaz.mombasawala@broadcom.com>
To: "Zack Rusin" <zack.rusin@broadcom.com>,
<dri-devel@lists.freedesktop.org>
Cc: <bcm-kernel-feedback-list@broadcom.com>,
<ian.forbes@broadcom.com>, <yunfeng.li.nb@gmail.com>,
<tomas@slax.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 1/6] drm/vmwgfx: keep cursor mappings and pins with each plane state
Date: Wed, 04 Nov 2026 18:40:25 -0800 [thread overview]
Message-ID: <DMMXHJ7E33NS.3QACG0ZSMROU5@broadcom.com> (raw)
In-Reply-To: <20261027211729.646988-2-zack.rusin@broadcom.com>
LGTM!
Reviewed-by: Maaz Mombasawala <maaz.mombasawala@broadcom.com>
--
Maaz Mombasawala <maaz.mombasawala@broadcom.com>
next prev parent reply other threads:[~2026-11-05 2:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261027211729.646988-1-zack.rusin@broadcom.com>
2026-10-27 21:17 ` [PATCH 1/6] drm/vmwgfx: keep cursor mappings and pins with each plane state Zack Rusin
2026-11-05 2:40 ` Maaz Mombasawala <maaz.mombasawala@broadcom.com> [this message]
2026-11-05 19:05 ` Ian Forbes
2026-11-05 22:24 ` Zack Rusin
2026-10-27 21:17 ` [PATCH 2/6] drm/vmwgfx: validate GB-only cursor command limits Zack Rusin
2026-11-05 2:38 ` Maaz Mombasawala <maaz.mombasawala@broadcom.com>
2026-11-07 1:43 ` Zack Rusin
2026-10-27 21:17 ` [PATCH 3/6] drm/vmwgfx: include legacy hotspots in GB-only cursor images Zack Rusin
2026-11-05 2:40 ` Maaz Mombasawala <maaz.mombasawala@broadcom.com>
2026-10-27 21:17 ` [PATCH 4/6] drm/vmwgfx: reserve dumb buffers while detaching their surfaces Zack Rusin
2026-11-05 2:40 ` Maaz Mombasawala <maaz.mombasawala@broadcom.com>
2026-10-27 21:17 ` [PATCH 5/6] drm/vmwgfx: validate the framebuffer selected for cursor updates Zack Rusin
2026-11-05 2:37 ` Maaz Mombasawala <maaz.mombasawala@broadcom.com>
2026-10-27 21:17 ` [PATCH 6/6] drm/vmwgfx: reserve cursor MOBs before unpinning them Zack Rusin
2026-11-05 2:40 ` Maaz Mombasawala <maaz.mombasawala@broadcom.com>
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=DMMXHJ7E33NS.3QACG0ZSMROU5@broadcom.com \
--to=maaz.mombasawala@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ian.forbes@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=tomas@slax.org \
--cc=yunfeng.li.nb@gmail.com \
--cc=zack.rusin@broadcom.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