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/4] drm/i915/color: Debug improvements and intel_display conversion
Date: Thu, 24 Oct 2024 20:20:25 +0300 [thread overview]
Message-ID: <878quds9ie.fsf@intel.com> (raw)
In-Reply-To: <20241024165356.17756-1-ville.syrjala@linux.intel.com>
On Thu, 24 Oct 2024, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Improve the debug prints in intel_color.c a bit, and convert it to
> intel_display while at it.
Series is
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Ville Syrjälä (4):
> drm/i915/color: Pimp debugs
> drm/i915: Handle intel_plane and intel_plane_state in
> to_intel_display()
> drm/i915/color: Convert color management code to intel_display
> drm/i915/color: Make color .get_config() mandatory
>
> drivers/gpu/drm/i915/display/intel_color.c | 673 +++++++++---------
> drivers/gpu/drm/i915/display/intel_color.h | 6 +-
> .../drm/i915/display/intel_display_driver.c | 4 +-
> .../drm/i915/display/intel_display_types.h | 8 +-
> 4 files changed, 356 insertions(+), 335 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-10-24 17:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 16:53 [PATCH 0/4] drm/i915/color: Debug improvements and intel_display conversion Ville Syrjala
2024-10-24 16:53 ` [PATCH 1/4] drm/i915/color: Pimp debugs Ville Syrjala
2024-10-24 16:53 ` [PATCH 2/4] drm/i915: Handle intel_plane and intel_plane_state in to_intel_display() Ville Syrjala
2024-10-24 16:53 ` [PATCH 3/4] drm/i915/color: Convert color management code to intel_display Ville Syrjala
2024-10-24 16:53 ` [PATCH 4/4] drm/i915/color: Make color .get_config() mandatory Ville Syrjala
2024-10-24 17:20 ` Jani Nikula [this message]
2024-10-24 17:25 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/color: Debug improvements and intel_display conversion Patchwork
2024-10-24 17:42 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-25 6:35 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/color: Debug improvements and intel_display conversion (rev2) Patchwork
2024-10-25 6:35 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-10-25 7:12 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-25 8:13 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-29 12:31 ` ✓ Fi.CI.BAT: success for drm/i915/color: Debug improvements and intel_display conversion (rev4) Patchwork
2024-10-29 12:32 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-10-29 12:32 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-10-29 15:37 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-30 20:11 ` 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=878quds9ie.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.