intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tdz@users.sourceforge.net>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tdz@users.sourceforge.net>,
	rodrigo.vivi@intel.com
Subject: [PATCH 0/5] drm/i915: Replace {un/reference} with {put, get} functions
Date: Mon, 18 Jun 2018 13:01:49 +0200	[thread overview]
Message-ID: <20180618110154.30462-1-tdz@users.sourceforge.net> (raw)

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.

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

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2018-06-18 11:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 11:01 Thomas Zimmermann [this message]
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-18 12:01 ` ✓ Fi.CI.BAT: success for drm/i915: Replace {un/reference} with {put, get} functions Patchwork
2018-06-18 14:56 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-06-26  9:02 ` ✓ Fi.CI.BAT: success " Patchwork
2018-06-26  9:54 ` ✓ Fi.CI.IGT: " Patchwork
2018-06-28 17:10 ` [PATCH 0/5] drm/i915: Replace {un/reference} with {put,get} functions 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=20180618110154.30462-1-tdz@users.sourceforge.net \
    --to=tdz@users.sourceforge.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).