linux-kernel - [PATCH 3/3] backlight: Remove old device_register and device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 Sep 2009 17:19:43 +0100
From:	Matthew Garrett <mjg@...hat.com>
To:	rpurdie@...ys.net
Cc:	linux-kernel@...r.kernel.org, Matthew Garrett <mjg@...hat.com>
Subject: [PATCH 3/3] backlight: Remove old device_register and device_unregister API

Now all the users are transitioned, the old functions can be removed.

Signed-off-by: Matthew Garrett <mjg@...hat.com>
---
 drivers/video/backlight/backlight.c |   48 -----------------------------------
 include/linux/backlight.h           |    3 --
 2 files changed, 0 insertions(+), 51 deletions(-)

diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c
index 9048a28..39ffa86 100644
--- a/drivers/video/backlight/backlight.c
+++ b/drivers/video/backlight/backlight.c
@@ -289,38 +289,6 @@ int backlight_register(struct backlight_device *bd)
 EXPORT_SYMBOL(backlight_register);
 
 /**
- * backlight_device_register - create and register a new object of
- *   backlight_device class.
- * @name: the name of the new object(must be the same as the name of the
- *   respective framebuffer device).
- * @parent: a pointer to the parent device
- * @devdata: an optional pointer to be stored for private driver use. The
- *   methods may retrieve it by using bl_get_data(bd).
- * @ops: the backlight operations structure.
- *
- * Creates and registers new backlight device. Returns either an
- * ERR_PTR() or a pointer to the newly allocated device.
- */
-struct backlight_device *backlight_device_register(const char *name,
-		struct device *parent, void *devdata, struct backlight_ops *ops)
-{
-	struct backlight_device *new_bd;
-	int rc;
-
-	new_bd = backlight_alloc(name, parent, devdata, ops);
-
-	if (IS_ERR(new_bd))
-		return new_bd;
-
-	rc = backlight_register(new_bd);
-	if (rc)
-		return ERR_PTR(rc);
-
-	return new_bd;
-}
-EXPORT_SYMBOL(backlight_device_register);
-
-/**
  * backlight_destroy - frees a backlight device object
  * @bd: the backlight device object to be freed.
  *
@@ -359,22 +327,6 @@ void backlight_unregister(struct backlight_device *bd)
 }
 EXPORT_SYMBOL(backlight_unregister);
 
-/**
- * backlight_device_unregister - unregisters a backlight device object.
- * @bd: the backlight device object to be unregistered and freed.
- *
- * Unregisters a previously registered via backlight_device_register object.
- */
-void backlight_device_unregister(struct backlight_device *bd)
-{
-	if (!bd)
-		return;
-
-	backlight_unregister(bd);
-	backlight_destroy(bd);
-}
-EXPORT_SYMBOL(backlight_device_unregister);
-
 static void __exit backlight_class_exit(void)
 {
 	class_destroy(backlight_class);
diff --git a/include/linux/backlight.h b/include/linux/backlight.h
index 9e17ff0..4c21b0b 100644
--- a/include/linux/backlight.h
+++ b/include/linux/backlight.h
@@ -98,13 +98,10 @@ static inline void backlight_update_status(struct backlight_device *bd)
 }
 
 
-extern struct backlight_device *backlight_device_register(const char *name,
-	struct device *dev, void *devdata, struct backlight_ops *ops);
 extern struct backlight_device *backlight_alloc(const char *name,
 	struct device *dev, void *devdata, struct backlight_ops *ops);
 extern int backlight_register(struct backlight_device *bd);
 
-extern void backlight_device_unregister(struct backlight_device *bd);
 extern void backlight_unregister(struct backlight_device *bd);
 extern void backlight_destroy(struct backlight_device *bd);
 
-- 
1.6.2.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/