linux-kernel - Re: [PATCH 1/5] regulator: Pass regulator init data as explict argument when registering

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:	Mon, 19 Jan 2009 17:37:48 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	pHilipp Zabel <philipp.zabel@...il.com>
Cc:	Liam Girdwood <lrg@...mlogic.co.uk>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] regulator: Pass regulator init data as explict argument when registering

On Mon, Jan 19, 2009 at 06:24:50PM +0100, pHilipp Zabel wrote:

> Good, I had a local patch that would pass bq24022_mach_info in
> regulator_init_data->driver_data instead of platform_data.
> Now that there is a possibility to pass platform_data, is there still
> need for the driver_data field in regulator_init_data and for the
> regulator_get_init_drvdata() function?

I'd not expect so, no.  The driver doesn't get to see the constraints.
--
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/