linux-kernel - Re: [PATCH 3/5] regulator: tps65910: use self device for regulator registration

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: <20120519180150.GA4039@opensource.wolfsonmicro.com>
Date:	Sat, 19 May 2012 19:01:51 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	lrg@...com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/5] regulator: tps65910:  use self device for regulator
 registration

On Sat, May 19, 2012 at 08:04:08PM +0530, Laxman Dewangan wrote:

> Use self device for regulator registration instead of parent
> device.

What's the motivation behind this change?  I'd expect the MFD device
(which is the actual physical device) to make things like dev_ prints
have an actual physical device which seems a bit more user friendly.  
Making this change will also mean that things like regulator to
regulator supplies are less obvious on non-DT systems as they'll wind up
having to specify the subdevice, and on DT systems it'll change the
binding from being for the parent device to the subdevice.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)