From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 08/10] drm: Extract drm_color_mgmt.[hc]
Date: Thu, 1 Sep 2016 10:51:09 +0100 [thread overview]
Message-ID: <53021f26-19e0-9100-6965-e525d5bec036@intel.com> (raw)
In-Reply-To: <20160831160913.12991-9-daniel.vetter@ffwll.ch>
[-- Attachment #1.1: Type: text/plain, Size: 781 bytes --]
On 31/08/16 17:09, Daniel Vetter wrote:
> For both the new degamm/lut/gamma atomic combo, and the old legacy
> gamma tables.
>
> Signed-off-by: Daniel Vetter<daniel.vetter@intel.com>
> ---
> drivers/gpu/drm/Makefile | 2 +-
> drivers/gpu/drm/drm_color_mgmt.c | 248 ++++++++++++++++++++++++++++++++++++
> drivers/gpu/drm/drm_crtc.c | 220 --------------------------------
> drivers/gpu/drm/drm_crtc_internal.h | 4 +
> include/drm/drm_color_mgmt.h | 56 ++++++++
> include/drm/drm_crtc.h | 28 +---
> 6 files changed, 310 insertions(+), 248 deletions(-)
> create mode 100644 drivers/gpu/drm/drm_color_mgmt.c
> create mode 100644 include/drm/drm_color_mgmt.h
Acked-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
[-- Attachment #1.2: Type: text/html, Size: 1296 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-01 9:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 16:09 [PATCH 00/10] More splitting&documenting for drm_crtc.c Daniel Vetter
2016-08-31 16:09 ` [PATCH 01/10] drm: Move a few macros away from drm_crtc.h Daniel Vetter
2016-09-06 16:59 ` [Intel-gfx] " Sean Paul
2016-09-08 0:05 ` Carlos Santa
2016-08-31 16:09 ` [PATCH 02/10] drm: Extract drm_bridge.h Daniel Vetter
2016-09-02 9:25 ` Archit Taneja
2016-08-31 16:09 ` [PATCH 03/10] drm: Move all decl for drm_edid.c to drm_edid.h Daniel Vetter
2016-09-06 16:59 ` Sean Paul
2016-09-19 14:28 ` Daniel Vetter
2016-08-31 16:09 ` [PATCH 04/10] drm: Extract drm_plane.[hc] Daniel Vetter
2016-09-06 16:59 ` [Intel-gfx] " Sean Paul
2016-09-19 13:11 ` Daniel Vetter
2016-09-21 7:32 ` Sean Paul
2016-08-31 16:09 ` [PATCH 05/10] drm/doc: Polish for drm_plane.[hc] Daniel Vetter
2016-09-02 9:30 ` Archit Taneja
2016-09-19 13:13 ` Daniel Vetter
2016-09-21 6:38 ` Archit Taneja
2016-08-31 16:09 ` [PATCH 06/10] drm: Conslidate blending properties in drm_blend.[hc] Daniel Vetter
2016-09-06 16:59 ` Sean Paul
2016-08-31 16:09 ` [PATCH 07/10] drm/doc: Polish plane composition property docs Daniel Vetter
2016-09-06 16:59 ` Sean Paul
2016-08-31 16:09 ` [PATCH 08/10] drm: Extract drm_color_mgmt.[hc] Daniel Vetter
2016-09-01 9:51 ` Lionel Landwerlin [this message]
2016-08-31 16:09 ` [PATCH 09/10] drm/doc: Document color space handling Daniel Vetter
2016-09-01 10:16 ` Lionel Landwerlin
2016-09-06 16:59 ` [Intel-gfx] " Sean Paul
2016-08-31 16:09 ` [PATCH 10/10] drm: Remove dirty property from docs Daniel Vetter
2016-09-06 16:59 ` Sean Paul
2016-09-01 9:20 ` ✗ Fi.CI.BAT: failure for More splitting&documenting for drm_crtc.c 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=53021f26-19e0-9100-6965-e525d5bec036@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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.