From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Zimmermann <tdz@users.sourceforge.net>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
rodrigo.vivi@intel.com
Subject: Re: [PATCH 0/5] drm/i915: Replace {un/reference} with {put,get} functions
Date: Thu, 28 Jun 2018 19:10:32 +0200 [thread overview]
Message-ID: <20180628171032.GY13978@phenom.ffwll.local> (raw)
In-Reply-To: <20180618110154.30462-1-tdz@users.sourceforge.net>
On Mon, Jun 18, 2018 at 01:01:49PM +0200, Thomas Zimmermann wrote:
> This patch set replaces functions named {un,reference} by their
> {put,get} counterparts. Affected data types are struct drm_connector,
> struct drm_gem_object, and struct drm_device.
>
> With the reference-counting functions being named {put,get}, the DRM
> interface is more aligned to Linux kernel nameing standard. The patch
> set does not change driver-internal interfaces.
Ok after kicking CI the spurious fail in the piglit tests is gone.
Everythign applied for 4.19, thanks a lot for your patches.
-Daniel
>
> Thomas Zimmermann (5):
> drm/i915: Replace drm_connector_{un/reference} with put,get functions
> drm/i915: Replace drm_gem_object_{un/reference} with {put,get}
> functions
> drm/i915: Replace __drm_gem_object_unreference with
> __drm_gem_object_put
> drm/i915: Replace drm_gem_object_unreference_unlocked with put
> function
> drm/i915: Replace drm_dev_unref with drm_dev_put
>
> drivers/gpu/drm/i915/i915_gem_object.h | 13 ++-----------
> drivers/gpu/drm/i915/intel_display.c | 4 ++--
> drivers/gpu/drm/i915/intel_dp_mst.c | 2 +-
> drivers/gpu/drm/i915/selftests/huge_pages.c | 2 +-
> drivers/gpu/drm/i915/selftests/i915_gem_context.c | 2 +-
> drivers/gpu/drm/i915/selftests/i915_gem_dmabuf.c | 2 +-
> drivers/gpu/drm/i915/selftests/i915_gem_evict.c | 2 +-
> drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 2 +-
> drivers/gpu/drm/i915/selftests/i915_gem_object.c | 2 +-
> drivers/gpu/drm/i915/selftests/i915_request.c | 2 +-
> drivers/gpu/drm/i915/selftests/i915_vma.c | 2 +-
> drivers/gpu/drm/i915/selftests/intel_breadcrumbs.c | 2 +-
> 12 files changed, 14 insertions(+), 23 deletions(-)
>
> --
> 2.14.4
>
--
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
prev parent reply other threads:[~2018-06-28 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 11:01 [PATCH 0/5] drm/i915: Replace {un/reference} with {put, get} functions Thomas Zimmermann
2018-06-18 11:01 ` [PATCH 1/5] drm/i915: Replace drm_connector_{un/reference} with put, get functions Thomas Zimmermann
2018-06-18 11:01 ` [PATCH 2/5] drm/i915: Replace drm_gem_object_{un/reference} with {put, get} functions Thomas Zimmermann
2018-06-18 11:01 ` [PATCH 3/5] drm/i915: Replace __drm_gem_object_unreference with __drm_gem_object_put Thomas Zimmermann
2018-06-18 11:01 ` [PATCH 4/5] drm/i915: Replace drm_gem_object_unreference_unlocked with put function Thomas Zimmermann
2018-06-18 11:01 ` [PATCH 5/5] drm/i915: Replace drm_dev_unref with drm_dev_put Thomas Zimmermann
2018-06-28 17:10 ` 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=20180628171032.GY13978@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=tdz@users.sourceforge.net \
/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