From: Daniel Vetter <daniel@ffwll.ch>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm: Nuke drm_framebuffer->helper_private
Date: Fri, 11 Sep 2015 09:18:58 +0200 [thread overview]
Message-ID: <20150911071858.GD31002@phenom.ffwll.local> (raw)
In-Reply-To: <CANq1E4TML5=dWcB8LWPgksKH9NS_HDQR9n1Lm1SKhNdCirYuZw@mail.gmail.com>
On Fri, Sep 11, 2015 at 03:47:25AM +0200, David Herrmann wrote:
> Hi
>
> On Thu, Sep 10, 2015 at 10:39 PM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > It's completely unused and there's really no reason for this:
> > - drm_framebuffer structures are invariant after creation, no need for
> > helpers to manipulate them.
> > - drm_framebuffer structures should just be embedded (and that's what
> > all the drivers do).
> >
> > Stumbled over this since some folks are apparently concerned with the
> > overhead of struct drm_framebuffer and this is an easy 8 byte saving.
> >
> > More could be gained by ditching the legacy fields and recomputing
> > stuff from the fourcc value. But that would require some drm-wide
> > cocci and real justification.
> >
> > Cc: gary.k.smith@intel.com
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > ---
> > include/drm/drm_crtc.h | 2 --
> > 1 file changed, 2 deletions(-)
>
> Reviewed-by: David Herrmann <dh.herrmann@gmail.com>
Thanks for the review, patch applied to drm-misc.
-Daniel
>
> Thanks
> David
>
> > diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> > index 75f49c1ef8bb..c0366e9152e2 100644
> > --- a/include/drm/drm_crtc.h
> > +++ b/include/drm/drm_crtc.h
> > @@ -210,8 +210,6 @@ struct drm_framebuffer {
> > int flags;
> > uint32_t pixel_format; /* fourcc format */
> > struct list_head filp_head;
> > - /* if you are using the helper */
> > - void *helper_private;
> > };
> >
> > struct drm_property_blob {
> > --
> > 2.5.1
> >
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-09-11 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 20:39 [PATCH] drm: Nuke drm_framebuffer->helper_private Daniel Vetter
2015-09-11 1:47 ` David Herrmann
2015-09-11 7:18 ` Daniel Vetter [this message]
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=20150911071858.GD31002@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dh.herrmann@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox