linux-kernel - Re: Applied "regulator: 88pm800: Remove owner" to the regulator tree

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] [day] [month] [year] [list]

Date:	Fri, 17 Jul 2015 12:56:06 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Applied "regulator: 88pm800: Remove owner" to the regulator tree

On Fri, Jul 17, 2015 at 06:58:32PM +0900, Krzysztof Kozlowski wrote:
> 2015-07-17 18:43 GMT+09:00 Mark Brown <broonie@...nel.org>:

> > The driver core apparently now does this and we shouldn't be doing it
> > statically so we get all this code churn.  I'm not sure I understand the
> > win TBH.

> If you are referring to my recent patchset it was about platform and
> i2c drivers where appropriate register functions do it (e.g.
> i2c_register_driver()). But regulator_register passes owner from
> regulator_desc:

It's not just your patch set, it's the latest thing in code churn.

> rdev->owner = regulator_desc->owner;
> and then calls device_register(). I think the owner for regulator
> device won't be set.

Oh, right yes.  Picked the wrong bit of code when merging a code motion
patch.

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