public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Noralf Trønnes" <noralf@tronnes.org>
To: dri-devel@lists.freedesktop.org
Cc: David1.Zhou@amd.com, oleksandr_andrushchenko@epam.com,
	intel-gfx@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	"Noralf Trønnes" <noralf@tronnes.org>,
	alexander.deucher@amd.com, airlied@redhat.com,
	christian.koenig@amd.com
Subject: [PATCH 6/6] drm/drv: Remove drm_dev_unplug()
Date: Sun,  3 Feb 2019 16:42:00 +0100	[thread overview]
Message-ID: <20190203154200.61479-7-noralf@tronnes.org> (raw)
In-Reply-To: <20190203154200.61479-1-noralf@tronnes.org>

There are no users left.

Signed-off-by: Noralf Trønnes <noralf@tronnes.org>
---
 drivers/gpu/drm/drm_drv.c | 17 -----------------
 include/drm/drm_drv.h     |  1 -
 2 files changed, 18 deletions(-)

diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index e0941200edc6..87210d4a9e53 100644
--- a/drivers/gpu/drm/drm_drv.c
+++ b/drivers/gpu/drm/drm_drv.c
@@ -354,23 +354,6 @@ void drm_dev_exit(int idx)
 }
 EXPORT_SYMBOL(drm_dev_exit);
 
-/**
- * drm_dev_unplug - unplug a DRM device
- * @dev: DRM device
- *
- * This unplugs a hotpluggable DRM device, which makes it inaccessible to
- * userspace operations. Entry-points can use drm_dev_enter() and
- * drm_dev_exit() to protect device resources in a race free manner. This
- * essentially unregisters the device like drm_dev_unregister(), but can be
- * called while there are still open users of @dev.
- */
-void drm_dev_unplug(struct drm_device *dev)
-{
-	drm_dev_unregister(dev);
-	drm_dev_put(dev);
-}
-EXPORT_SYMBOL(drm_dev_unplug);
-
 /*
  * DRM internal mount
  * We want to be able to allocate our own "struct address_space" to control
diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h
index c50696c82a42..b8765a6fc092 100644
--- a/include/drm/drm_drv.h
+++ b/include/drm/drm_drv.h
@@ -730,7 +730,6 @@ void drm_dev_put(struct drm_device *dev);
 void drm_put_dev(struct drm_device *dev);
 bool drm_dev_enter(struct drm_device *dev, int *idx);
 void drm_dev_exit(int idx);
-void drm_dev_unplug(struct drm_device *dev);
 
 /**
  * drm_dev_is_unplugged - is a DRM device unplugged
-- 
2.20.1

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

  parent reply	other threads:[~2019-02-03 15:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 15:41 [PATCH 0/6] drm/drv: Remove drm_dev_unplug() Noralf Trønnes
2019-02-03 15:41 ` [PATCH 1/6] drm: Fix drm_release() and device unplug Noralf Trønnes
     [not found]   ` <20190203154200.61479-2-noralf-L59+Z2yzLopAfugRpC6u6w@public.gmane.org>
2019-02-04 10:17     ` Oleksandr Andrushchenko
2019-02-07 21:00     ` Sean Paul
2019-02-03 15:41 ` [PATCH 2/6] drm/drv: Prepare to remove drm_dev_unplug() Noralf Trønnes
     [not found]   ` <20190203154200.61479-3-noralf-L59+Z2yzLopAfugRpC6u6w@public.gmane.org>
2019-02-04 10:19     ` Oleksandr Andrushchenko
2019-02-04 15:41     ` [Intel-gfx] " Daniel Vetter
     [not found]       ` <20190204154153.GT3271-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-02-04 17:35         ` Noralf Trønnes
     [not found]           ` <fd6ab7d7-2f50-14bb-07f4-b25c9fe0892e-L59+Z2yzLopAfugRpC6u6w@public.gmane.org>
2019-02-05  9:11             ` Daniel Vetter
     [not found]               ` <20190205091118.GC3271-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-02-05 10:20                 ` Noralf Trønnes
2019-02-05 16:31                   ` Daniel Vetter
     [not found]                     ` <20190205163144.GF3271-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-02-05 17:57                       ` Noralf Trønnes
2019-02-06 15:26                         ` Daniel Vetter
     [not found]                           ` <20190206152626.GI3271-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-02-06 16:46                             ` [Intel-gfx] " Noralf Trønnes
2019-02-06 20:36                               ` Daniel Vetter
2019-02-06 18:10                             ` [Intel-gfx] " Eric Anholt
2019-02-07 21:07     ` Sean Paul
2019-02-07 21:52       ` Sean Paul
2019-02-03 15:41 ` [PATCH 3/6] drm/amd: Use drm_dev_unregister() Noralf Trønnes
2019-02-03 15:41 ` [PATCH 4/6] drm/udl: " Noralf Trønnes
2019-02-07 21:07   ` Sean Paul
2019-02-03 15:41 ` [PATCH 5/6] drm/xen: " Noralf Trønnes
     [not found]   ` <20190203154200.61479-6-noralf-L59+Z2yzLopAfugRpC6u6w@public.gmane.org>
2019-02-04 10:42     ` Oleksandr Andrushchenko
2019-02-04 13:13       ` Noralf Trønnes
2019-02-03 15:42 ` Noralf Trønnes [this message]
     [not found]   ` <20190203154200.61479-7-noralf-L59+Z2yzLopAfugRpC6u6w@public.gmane.org>
2019-02-04 10:44     ` [PATCH 6/6] drm/drv: Remove drm_dev_unplug() Oleksandr Andrushchenko
2019-02-07 21:08     ` Sean Paul
2019-02-03 16:12 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-02-03 17:59 ` ✓ Fi.CI.IGT: " Patchwork
2019-02-04 10:05 ` [PATCH 0/6] " Daniel Vetter
2019-02-04 12:45 ` Koenig, Christian

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=20190203154200.61479-7-noralf@tronnes.org \
    --to=noralf@tronnes.org \
    --cc=David1.Zhou@amd.com \
    --cc=airlied@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=oleksandr_andrushchenko@epam.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