From: Xaver Hugl <xaver.hugl@gmail.com>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/6] drm/uapi: Document CTM matrix better
Date: Fri, 28 Apr 2023 00:31:10 +0200 [thread overview]
Message-ID: <3e6ce087-411a-8f2e-974e-2a9379587159@gmail.com> (raw)
In-Reply-To: <20230411222931.15127-2-ville.syrjala@linux.intel.com>
I can't say anything about the other commits in this series, but
"Document in which order the CTM matrix elements are stored" is
Reviewed-by: Xaver Hugl <xaver.hugl@gmail.com>
next prev parent reply other threads:[~2023-05-01 12:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 22:29 [Intel-gfx] [PATCH 0/6] drm/i915: CTM stuff mostly Ville Syrjala
2023-04-11 22:29 ` [Intel-gfx] [PATCH 1/6] drm/uapi: Document CTM matrix better Ville Syrjala
2023-04-27 22:31 ` Xaver Hugl [this message]
2023-04-28 13:39 ` Ville Syrjälä
2023-04-28 9:27 ` Simon Ser
2023-04-11 22:29 ` [Intel-gfx] [PATCH 2/6] drm/i915: Expose crtc CTM property on ilk/snb Ville Syrjala
2023-04-11 22:29 ` [Intel-gfx] [PATCH 3/6] drm/i915: Fix CHV CGM CSC coefficient sign handling Ville Syrjala
2023-04-11 22:29 ` [Intel-gfx] [PATCH 4/6] drm/i915: Implement CTM property support for VLV Ville Syrjala
2023-04-11 22:29 ` [Intel-gfx] [PATCH 5/6] drm/i915: No 10bit gamma on desktop gen3 parts Ville Syrjala
2023-04-11 22:29 ` [Intel-gfx] [PATCH 6/6] drm/i915: Do state check for color management changes Ville Syrjala
2023-04-12 1:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTM stuff mostly Patchwork
2023-04-12 1:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-12 2:15 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-04-12 6:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTM stuff mostly (rev2) Patchwork
2023-04-12 6:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-12 6:27 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-04-13 5:50 ` Patchwork
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=3e6ce087-411a-8f2e-974e-2a9379587159@gmail.com \
--to=xaver.hugl@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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