linux-kernel - Re: [PATCH] regulator: Allow consumer supplies to be set up with dev

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:	Thu, 18 Jun 2009 11:54:03 +0100
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, Mike Rapoport <mike@...pulab.co.il>
Subject: Re: [PATCH] regulator: Allow consumer supplies to be set up with
 dev_name()

On Wed, 2009-06-17 at 17:56 +0100, Mark Brown wrote:
> Follow the approach suggested by Russell King and implemented by him in
> the clkdev API and allow consumer device supply mapings to be set up
> using the dev_name() for the consumer instead of the struct device.
> In order to avoid making existing machines instabuggy and creating merge
> issues the use of struct device is still supported for the time being.
> 

We should probably mark this as deprecated in the docs.

> This resolves problems working with buses such as I2C which make the
> struct device available late providing that the final device name is
> known, which is the case for most embedded systems with fixed setups.
> 
> Consumers must still use the struct device when calling regulator_get().
> 
> Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> ---
> For the avoidance of doubt this is most definately 2.6.32 material, not
> 2.6.31.
> 
>  drivers/regulator/core.c          |   62 ++++++++++++++++++++++++++++--------
>  include/linux/regulator/machine.h |    7 +++-
>  2 files changed, 54 insertions(+), 15 deletions(-)
> 

Applied.

Thanks

Liam

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