Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Julia Lawall <julia.lawall@lip6.fr>,
	Dave Airlie <airlied@redhat.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 07/10] drm/virtio: Drop dummy gamma table support
Date: Tue, 12 Apr 2016 16:27:54 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1604121625210.2894@hadrien> (raw)
In-Reply-To: <CACvgo52o-YJcvW6rKfmWzVvOQZqQ=Yi9HO94bo7bNOSQ5oubgA@mail.gmail.com>



On Tue, 12 Apr 2016, Emil Velikov wrote:

> On 30 March 2016 at 10:51, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > No need to confuse userspace like this.
> >
> > Cc: Gerd Hoffmann <kraxel@redhat.com>
> > Cc: Dave Airlie <airlied@redhat.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > ---
> >  drivers/gpu/drm/virtio/virtgpu_display.c | 9 ---------
> >  1 file changed, 9 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c b/drivers/gpu/drm/virtio/virtgpu_display.c
> > index 4854dac87e24..12b72e29678a 100644
> > --- a/drivers/gpu/drm/virtio/virtgpu_display.c
> > +++ b/drivers/gpu/drm/virtio/virtgpu_display.c
> > @@ -38,13 +38,6 @@
> >  #define XRES_MAX  8192
> >  #define YRES_MAX  8192
> >
> > -static void virtio_gpu_crtc_gamma_set(struct drm_crtc *crtc,
> > -                                     u16 *red, u16 *green, u16 *blue,
> > -                                     uint32_t start, uint32_t size)
> > -{
> > -       /* TODO */
> > -}
> > -
> >  static void
> >  virtio_gpu_hide_cursor(struct virtio_gpu_device *vgdev,
> >                        struct virtio_gpu_output *output)
> > @@ -173,7 +166,6 @@ static int virtio_gpu_page_flip(struct drm_crtc *crtc,
> >  static const struct drm_crtc_funcs virtio_gpu_crtc_funcs = {
> >         .cursor_set2            = virtio_gpu_crtc_cursor_set,
> >         .cursor_move            = virtio_gpu_crtc_cursor_move,
> > -       .gamma_set              = virtio_gpu_crtc_gamma_set,
> >         .set_config             = drm_atomic_helper_set_config,
> >         .destroy                = drm_crtc_cleanup,
> >
> > @@ -416,7 +408,6 @@ static int vgdev_output_init(struct virtio_gpu_device *vgdev, int index)
> >                 return PTR_ERR(plane);
> >         drm_crtc_init_with_planes(dev, crtc, plane, NULL,
> >                                   &virtio_gpu_crtc_funcs, NULL);
> > -       drm_mode_crtc_set_gamma_size(crtc, 256);
> >         drm_crtc_helper_add(crtc, &virtio_gpu_crtc_helper_funcs);
> >         plane->crtc = crtc;
> >
> Out of curiosity:
>
> Coccinelle should be able to handle/generate such patches, shouldn't
> it ? I believe in the past people used it for similar
> refactoring/cleanups, yet not (m)any of them [the cocci files] got
> checked in the kernel tree.
>
> Thinking about future drivers derived from outdated sources - do you
> think it's a good/bad idea to check/run them along side the existing
> ones ?

The issue is that there is no point to put an empty function in a
structure?

It would be a bit subtle for Coccinelle, because it requires also knowing
that one is allowed to leave that particular field empty.

julia
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-04-12 14:27 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 [this message]
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
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=alpine.DEB.2.10.1604121625210.2894@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox