From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Harry Wentland <harry.wentland@amd.com>,
<dri-devel@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Cc: <contact@emersion.fr>, <alex.hung@amd.com>,
<daniels@collabora.com>, <mwen@igalia.com>,
<sebastian.wick@redhat.com>, <uma.shankar@intel.com>,
<ville.syrjala@linux.intel.com>,
<maarten.lankhorst@linux.intel.com>, <jani.nikula@intel.com>,
<louis.chauvet@bootlin.com>, <stable@vger.kernel.org>,
"Kandpal, Suraj" <suraj.kandpal@intel.com>
Subject: Re: [PATCH v2 0/2] drm/colorop: Keep colorop state consistent across atomic commits
Date: Mon, 16 Mar 2026 12:59:45 +0530 [thread overview]
Message-ID: <ff8869ea-47cf-4b02-8173-7f3b0928585d@intel.com> (raw)
In-Reply-To: <a0ec2ae2-502a-4587-8951-41dca92fc8c6@amd.com>
Hello Harry,
On 3/14/2026 2:15 AM, Harry Wentland wrote:
> Would you like me to pull these into drm-misc-next? I'd love
> the changes as base for me next patchset.
Thank you for the reviews. Suraj(in cc) already merged them through
drm-misc, they should already be in.
==
Chaitanya
prev parent reply other threads:[~2026-03-16 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 11:32 [PATCH v2 0/2] drm/colorop: Keep colorop state consistent across atomic commits Chaitanya Kumar Borah
2026-03-10 11:32 ` [PATCH v2 1/2] drm/colorop: Preserve bypass value in duplicate_state() Chaitanya Kumar Borah
2026-03-12 19:16 ` Harry Wentland
2026-03-10 11:32 ` [PATCH v2 2/2] drm/atomic: Add affected colorops with affected planes Chaitanya Kumar Borah
2026-03-12 19:17 ` Harry Wentland
2026-03-13 20:45 ` [PATCH v2 0/2] drm/colorop: Keep colorop state consistent across atomic commits Harry Wentland
2026-03-16 7:29 ` Borah, Chaitanya Kumar [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=ff8869ea-47cf-4b02-8173-7f3b0928585d@intel.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=alex.hung@amd.com \
--cc=contact@emersion.fr \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mwen@igalia.com \
--cc=sebastian.wick@redhat.com \
--cc=stable@vger.kernel.org \
--cc=suraj.kandpal@intel.com \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@linux.intel.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