From: Daniel Vetter <daniel@ffwll.ch>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Thierry Reding <treding@nvidia.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 10/10] drm/tegra: Don't set a gamma table size
Date: Wed, 30 Mar 2016 17:31:09 +0200 [thread overview]
Message-ID: <20160330153109.GN2510@phenom.ffwll.local> (raw)
In-Reply-To: <20160330123922.GD2329@ulmo>
On Wed, Mar 30, 2016 at 02:39:22PM +0200, Thierry Reding wrote:
> On Wed, Mar 30, 2016 at 11:51:25AM +0200, Daniel Vetter wrote:
> > tegra doesn't have any functions to set gamma tables, so this is
> > completely defunct.
> >
> > Not nice to lie to userspace, so let's stop!
> >
> > Cc: Thierry Reding <treding@nvidia.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > ---
> > drivers/gpu/drm/tegra/dc.c | 1 -
> > 1 file changed, 1 deletion(-)
>
> Do you want this to go through the Tegra tree or do you have follow-up
> work that depends on this?
Driver trees is fine, pls just confirm when you do so (to make sure I
don't accidentally merge it too).
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-03-30 15:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 9:51 [PATCH 00/10] legacy gamma code cleanup Daniel Vetter
2016-03-30 9:51 ` [PATCH 01/10] drm: Initialize a linear gamma table by default Daniel Vetter
2016-05-31 13:05 ` Maarten Lankhorst
2016-05-31 13:24 ` Daniel Vetter
2016-05-31 13:30 ` Maarten Lankhorst
2016-03-30 9:51 ` [PATCH 02/10] drm/fb-helper: Remove dead code in setcolreg Daniel Vetter
2016-05-31 13:09 ` Maarten Lankhorst
2016-05-31 13:25 ` Daniel Vetter
2016-03-30 9:51 ` [PATCH 03/10] drm/armada: Drop fb gamma_set/get functions Daniel Vetter
2016-03-30 11:09 ` Russell King - ARM Linux
2016-03-30 11:19 ` Daniel Vetter
2016-03-30 12:56 ` Russell King - ARM Linux
2016-03-30 15:29 ` Daniel Vetter
2016-03-30 9:51 ` [PATCH 04/10] drm/bochs: Drop fake gamma support Daniel Vetter
2016-04-01 8:37 ` Gerd Hoffmann
2016-03-30 9:51 ` [PATCH 05/10] drm/cirrus: Drop redundnant gamma size check Daniel Vetter
2016-05-31 13:11 ` Maarten Lankhorst
2016-03-30 9:51 ` [PATCH 06/10] drm/msm: Nuke dummy gamma_set/get functions Daniel Vetter
2016-05-31 13:18 ` Maarten Lankhorst
2016-03-30 9:51 ` [PATCH 07/10] drm/virtio: Drop dummy gamma table support Daniel Vetter
2016-04-01 8:38 ` Gerd Hoffmann
2016-04-12 11:14 ` Daniel Vetter
2016-04-12 13:58 ` Emil Velikov
2016-04-12 14:27 ` Julia Lawall
2016-03-30 9:51 ` [PATCH 08/10] drm/imx: Don't set a gamma table size Daniel Vetter
2016-03-30 13:36 ` Philipp Zabel
2016-03-30 9:51 ` [PATCH 09/10] drm/qxl: " Daniel Vetter
2016-05-31 13:17 ` Maarten Lankhorst
2016-05-31 13:27 ` Daniel Vetter
2016-03-30 9:51 ` [PATCH 10/10] drm/tegra: " Daniel Vetter
2016-03-30 12:39 ` Thierry Reding
2016-03-30 15:31 ` Daniel Vetter [this message]
2016-03-31 10:33 ` Thierry Reding
2016-03-31 7:15 ` ✗ Fi.CI.BAT: failure for legacy gamma code cleanup 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=20160330153109.GN2510@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.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