From: Jani Nikula <jani.nikula@intel.com>
To: ville.syrjala@linux.intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm: constify all struct drm_encoder_helper_funcs pointers
Date: Tue, 10 Mar 2015 17:19:09 +0200 [thread overview]
Message-ID: <87385cswwi.fsf@intel.com> (raw)
In-Reply-To: <ae75e838a2391a4e0a5e403b052d961c2ab9aaed.1426000252.git.jani.nikula@intel.com>
On Tue, 10 Mar 2015, Jani Nikula <jani.nikula@intel.com> wrote:
> - const struct drm_encoder_helper_funcs *funcs;
> + const const struct drm_encoder_helper_funcs *funcs;
Obviously too quick cocci all around for double consting, but this was
to get feedback anyway. I also missed the helper_private in drm_plane.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-10 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 12:35 [PATCH] drm/atomic: Constify a bunch of functions pointer structs ville.syrjala
2015-03-10 15:14 ` [PATCH 0/4] drm: constify all helper_private/func pointers Jani Nikula
2015-03-10 15:14 ` [PATCH 1/4] drm: constify all struct drm_encoder_helper_funcs pointers Jani Nikula
2015-03-10 15:19 ` Jani Nikula [this message]
2015-03-10 15:15 ` [PATCH 2/4] drm: constify all struct drm_connector_helper_funcs pointers Jani Nikula
2015-03-10 15:15 ` [PATCH 3/4] drm: constify all struct drm_crtc_helper_funcs pointers Jani Nikula
2015-03-10 15:15 ` [PATCH 4/4] drm: make encoder/connector/crtc helper_private a const pointer Jani Nikula
2015-03-10 15:34 ` [PATCH 0/4] drm: constify all helper_private/func pointers Ville Syrjälä
2015-03-11 7:33 ` 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=87385cswwi.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ville.syrjala@linux.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