From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm/i915: intel_color_check() cleanup
Date: Fri, 24 May 2024 12:17:18 +0300 [thread overview]
Message-ID: <877cfjo9gh.fsf@intel.com> (raw)
In-Reply-To: <20240523182818.15382-1-ville.syrjala@linux.intel.com>
On Thu, 23 May 2024, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Eliminate the crtc_state->state footgun from intel_color_check(),
> and hide some mundane C8 plane details inside it.
On the series,
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Ville Syrjälä (3):
> drm/i915: Plumb the entire atomic state into intel_color_check()
> drm/i915: Hide the intel_crtc_needs_color_update() inside
> intel_color_check()
> drm/i915: Bury c8_planes_changed() in intel_color_check()
>
> drivers/gpu/drm/i915/display/intel_color.c | 125 ++++++++++++-------
> drivers/gpu/drm/i915/display/intel_color.h | 4 +-
> drivers/gpu/drm/i915/display/intel_display.c | 26 +---
> 3 files changed, 85 insertions(+), 70 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-05-24 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 18:28 [PATCH 0/3] drm/i915: intel_color_check() cleanup Ville Syrjala
2024-05-23 18:28 ` [PATCH 1/3] drm/i915: Plumb the entire atomic state into intel_color_check() Ville Syrjala
2024-05-23 18:28 ` [PATCH 2/3] drm/i915: Hide the intel_crtc_needs_color_update() inside intel_color_check() Ville Syrjala
2024-05-23 18:28 ` [PATCH 3/3] drm/i915: Bury c8_planes_changed() in intel_color_check() Ville Syrjala
2024-05-23 19:39 ` ✗ Fi.CI.SPARSE: warning for drm/i915: intel_color_check() cleanup Patchwork
2024-05-23 19:48 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-24 9:17 ` Jani Nikula [this message]
2024-05-24 21:40 ` ✗ Fi.CI.IGT: failure " 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=877cfjo9gh.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.