linux-kernel - RE: [PATCH v4] regulator: Add S5M8767A regulator driver

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]

Message-id: <01d901cccea9$af3b8490$0db28db0$@com>
Date:	Mon, 09 Jan 2012 17:35:47 +0900
From:	Sangbeom Kim <sbkim73@...sung.com>
To:	'Mark Brown' <broonie@...nsource.wolfsonmicro.com>
Cc:	lrg@...com, sameo@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: RE: [PATCH v4] regulator: Add S5M8767A regulator driver

Hi,
On Mon, Jan 9, 2011 at 04:25PM, Mark Brown wrote:

> I was expecting a new version with these:
> 
> > +static int s5m8767_reg_enable_suspend(struct regulator_dev *rdev)
> > +static int s5m8767_reg_disable_suspend(struct regulator_dev *rdev)
> 

After delete above functions, Is it right to code like below?

+static struct regulator_ops s5m8767_buck_ops = {
+	.enable	 = s5m8767_reg_enable,
+	.disable	 = s5m8767_reg_disable,
+	.set_suspend_enable	= s5m8767_reg_enable,
+	.set_suspend_disable	= s5m8767_reg_disable,

Thanks,
Sangbeom.

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