dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 0/6] drm: Introduce consistent reference counting APIs
Date: Thu, 09 Feb 2017 16:10:12 +0200	[thread overview]
Message-ID: <87r337sbej.fsf@intel.com> (raw)
In-Reply-To: <20170208182408.5442-1-thierry.reding@gmail.com>

On Wed, 08 Feb 2017, Thierry Reding <thierry.reding@gmail.com> wrote:
> This series introduces DRM reference counting APIs that are consistent
> with other reference counting APIs in the kernel. They are also much
> shorter. Compatibility aliases are added to keep existing code working
> and will stay in place until all users of the old APIs are gone.

I like it.

But it makes drm_connector_list_iter_{get,put} stick out like a sore
thumb. Something for the TODO list I guess.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-02-09 14:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 18:24 [PATCH 0/6] drm: Introduce consistent reference counting APIs Thierry Reding
2017-02-08 18:24 ` [PATCH 1/6] drm: Rename drm_mode_object_get() Thierry Reding
2017-02-08 19:23   ` Sean Paul
2017-02-08 18:24 ` [PATCH 2/6] drm: Introduce drm_mode_object_{get,put}() Thierry Reding
2017-02-08 19:28   ` Sean Paul
2017-02-09 17:08     ` Daniel Vetter
2017-02-09 20:41       ` Thierry Reding
2017-02-09 21:55         ` Emil Velikov
2017-02-14 20:12           ` Daniel Vetter
2017-02-08 18:24 ` [PATCH 3/6] drm: Introduce drm_connector_{get,put}() Thierry Reding
2017-02-08 19:33   ` Sean Paul
2017-02-08 18:24 ` [PATCH 4/6] drm: Introduce drm_framebuffer_{get,put}() Thierry Reding
2017-02-08 19:36   ` Sean Paul
2017-02-08 18:24 ` [PATCH 5/6] drm: Introduce drm_gem_object_{get,put}() Thierry Reding
2017-02-08 19:41   ` Sean Paul
2017-02-08 18:24 ` [PATCH 6/6] drm: Introduce drm_property_blob_{get,put}() Thierry Reding
2017-02-08 19:45   ` Sean Paul
2017-02-09 14:10 ` Jani Nikula [this message]
2017-02-09 17:09   ` [PATCH 0/6] drm: Introduce consistent reference counting APIs Daniel Vetter
2017-02-09 17:39     ` Jani Nikula
2017-02-09 19:07       ` Daniel Vetter
2017-02-09 20:39         ` Thierry Reding
2017-02-10  7:29           ` Jani Nikula
2017-02-10 15:58             ` Daniel Vetter
2017-02-10 14:47 ` Christian König

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=87r337sbej.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).