linux-kernel - [PATCH] regulator: make sure the regulator is available prior to the consumers.

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]

Date:	Thu, 10 Jun 2010 16:53:47 +0800
From:	sonic zhang <sonic.adi@...il.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...mlogic.co.uk>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>,
	uclinux-dist-devel <uclinux-dist-devel@...ckfin.uclinux.org>
Subject: [PATCH] regulator: make sure the regulator is available prior to
	the consumers.

>>From 5a71b38961b0889a239842defd733774ed3d9cdf Mon Sep 17 00:00:00 2001
From: Sonic Zhang <sonic.zhang@...log.com>
Date: Thu, 10 Jun 2010 16:50:20 +0800
Subject: [PATCH] regulator: make sure the regulator is available prior to the consumers.

Some systems are likely to want this to be subsys_initcall() to
make sure the regulator is available prior to the consumers.

Signed-off-by: Sonic Zhang <sonic.zhang@...log.com>
---
 drivers/regulator/ad5398.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/regulator/ad5398.c b/drivers/regulator/ad5398.c
index 0451c30..03969d3 100644
--- a/drivers/regulator/ad5398.c
+++ b/drivers/regulator/ad5398.c
@@ -274,7 +274,7 @@ static int __init ad5398_init(void)
 {
 	return i2c_add_driver(&ad5398_driver);
 }
-module_init(ad5398_init);
+subsys_initcall(ad5398_init);
 
 static void __exit ad5398_exit(void)
 {
-- 
1.6.0



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