linux-kernel - [PATCH 1/4] power-supply: smb347-charger: convert to use module_i2c

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-next>] [day] [month] [year] [list]

Message-Id: <1334566121-8243-1-git-send-email-mika.westerberg@linux.intel.com>
Date:	Mon, 16 Apr 2012 11:48:38 +0300
From:	Mika Westerberg <mika.westerberg@...ux.intel.com>
To:	linux-kernel@...r.kernel.org
Cc:	anton.vorontsov@...aro.org, alan@...ux.intel.com,
	bruce.e.robertson@...el.com,
	Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: [PATCH 1/4] power-supply: smb347-charger: convert to use module_i2c_driver()

This reduces the amount of boilerplate code in the driver and makes it a bit
simpler.

Signed-off-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
---
 drivers/power/smb347-charger.c |   12 +-----------
 1 files changed, 1 insertions(+), 11 deletions(-)

diff --git a/drivers/power/smb347-charger.c b/drivers/power/smb347-charger.c
index ce1694d..066794d 100644
--- a/drivers/power/smb347-charger.c
+++ b/drivers/power/smb347-charger.c
@@ -1275,17 +1275,7 @@ static struct i2c_driver smb347_driver = {
 	.id_table     = smb347_id,
 };
 
-static int __init smb347_init(void)
-{
-	return i2c_add_driver(&smb347_driver);
-}
-module_init(smb347_init);
-
-static void __exit smb347_exit(void)
-{
-	i2c_del_driver(&smb347_driver);
-}
-module_exit(smb347_exit);
+module_i2c_driver(smb347_driver);
 
 MODULE_AUTHOR("Bruce E. Robertson <bruce.e.robertson@...el.com>");
 MODULE_AUTHOR("Mika Westerberg <mika.westerberg@...ux.intel.com>");
-- 
1.7.9.1

--
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/