From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 00/10] drm/i915: Clean up intel_color_check()
Date: Thu, 28 Mar 2019 21:33:37 +0200 [thread overview]
Message-ID: <20190328193337.GN3888@intel.com> (raw)
In-Reply-To: <20190327173018.GS4773@mdroper-desk.amr.corp.intel.com>
On Wed, Mar 27, 2019 at 10:30:18AM -0700, Matt Roper wrote:
> On Wed, Mar 27, 2019 at 05:50:35PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Repost of the earlier series to clean up intel_color_check().
> > I tried to address all of Matt's review comments (thanks!).
> >
> > All reviewed except patch 8.
>
> Patch 8 (and the rest of the series):
>
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
Awesome. Thanks for reviewing this. Series pushed to dinq.
>
> > Ville Syrjälä (10):
> > drm/i915: Extract check_luts()
> > drm/i915: Turn intel_color_check() into a vfunc
> > drm/i915: Extract i9xx_color_check()
> > drm/i915: Extract chv_color_check()
> > drm/i915: Extract icl_color_check()
> > drm/i915: Extract glk_color_check()
> > drm/i915: Extract bdw_color_check()
> > drm/i915: Extract ilk_color_check()
> > drm/i915: Drop the pointless linear legacy LUT load on CHV
> > drm/i915: Skip the linear degamma LUT load on ICL+
> >
> > drivers/gpu/drm/i915/i915_drv.h | 1 +
> > drivers/gpu/drm/i915/intel_color.c | 416 +++++++++++++++++++++--------
> > 2 files changed, 311 insertions(+), 106 deletions(-)
> >
> > --
> > 2.19.2
> >
>
> --
> Matt Roper
> Graphics Software Engineer
> IoTG Platform Enabling & Development
> Intel Corporation
> (916) 356-2795
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-28 19:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 15:50 [PATCH v2 00/10] drm/i915: Clean up intel_color_check() Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 01/10] drm/i915: Extract check_luts() Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 02/10] drm/i915: Turn intel_color_check() into a vfunc Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 03/10] drm/i915: Extract i9xx_color_check() Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 04/10] drm/i915: Extract chv_color_check() Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 05/10] drm/i915: Extract icl_color_check() Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 06/10] drm/i915: Extract glk_color_check() Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 07/10] drm/i915: Extract bdw_color_check() Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 08/10] drm/i915: Extract ilk_color_check() Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 09/10] drm/i915: Drop the pointless linear legacy LUT load on CHV Ville Syrjala
2019-03-27 15:50 ` [PATCH v2 10/10] drm/i915: Skip the linear degamma LUT load on ICL+ Ville Syrjala
2019-03-27 17:30 ` [PATCH v2 00/10] drm/i915: Clean up intel_color_check() Matt Roper
2019-03-28 19:33 ` Ville Syrjälä [this message]
2019-03-27 20:07 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Clean up intel_color_check() (rev2) Patchwork
2019-03-27 21:00 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-28 17:38 ` ✓ Fi.CI.IGT: " 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=20190328193337.GN3888@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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