From: Rob Bradford <robert.bradford@intel.com>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/5] Pipe level color management V10
Date: Tue, 08 Mar 2016 11:45:41 +0000 [thread overview]
Message-ID: <1457437541.6682.18.camel@intel.com> (raw)
In-Reply-To: <1456506302-640-1-git-send-email-lionel.g.landwerlin@intel.com>
On Fri, 2016-02-26 at 17:04 +0000, Lionel Landwerlin wrote:
> This series introduces pipe level color management through a set of
> properties
> attached to the CRTC. It also provides an implementation for some
> Intel
> platforms.
> > This series is based of a previous set of patches by Shashank Sharma.
Acked-by: Rob Bradford <robert.bradford@intel.com>
Userspace parts that use DRM API are lgtm'ed by chromium OWNERS at:
https://codereview.chromium.org/1182063002/
Rob
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-08 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 17:04 [PATCH 0/5] Pipe level color management V10 Lionel Landwerlin
2016-02-26 17:04 ` [PATCH 1/5] drm/i915: Extract out gamma table and CSC to their own file Lionel Landwerlin
2016-02-26 17:04 ` [PATCH 2/5] drm/i915: Do not read GAMMA_MODE register Lionel Landwerlin
2016-02-26 17:05 ` [PATCH 3/5] drm: introduce pipe color correction properties Lionel Landwerlin
2016-03-22 9:59 ` Jani Nikula
2016-02-26 17:05 ` [PATCH 4/5] drm/i915: Implement color management on bdw/skl/bxt/kbl Lionel Landwerlin
2016-02-26 17:05 ` [PATCH 5/5] drm/i915: Implement color management on chv Lionel Landwerlin
2016-02-27 6:58 ` ✗ Fi.CI.BAT: failure for Pipe level color management (rev10) Patchwork
2016-03-08 11:45 ` Rob Bradford [this message]
2016-03-08 12:13 ` [PATCH 0/5] Pipe level color management V10 Daniel Stone
2016-03-08 12:59 ` Daniel Vetter
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=1457437541.6682.18.camel@intel.com \
--to=robert.bradford@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@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;
as well as URLs for NNTP newsgroup(s).