linux-kernel - Re: [PATCH] regulator: core: Clean enabling always-on regulators + their supplies

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: <20181211005221.GB3004@sirena.org.uk>
Date:   Tue, 11 Dec 2018 00:52:21 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Doug Anderson <dianders@...omium.org>
Cc:     linux-arm-msm <linux-arm-msm@...r.kernel.org>,
        Dmitry Osipenko <digetx@...il.com>,
        Evan Green <evgreen@...omium.org>, masneyb@...tation.org,
        Liam Girdwood <lgirdwood@...il.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] regulator: core: Clean enabling always-on regulators +
 their supplies

On Mon, Dec 10, 2018 at 08:32:32AM -0800, Doug Anderson wrote:
> On Mon, Dec 10, 2018 at 7:43 AM Mark Brown <broonie@...nel.org> wrote:

> > On Thu, Dec 06, 2018 at 02:23:18PM -0800, Douglas Anderson wrote:
> > > At the end of regulator_resolve_supply() we have historically turned
> > > on our supply in some cases.  This could be for one of two reasons:

> > This doesn't apply against current code, please check and resend.

> Can you clarify?  See below where it's applying cleanly to "for-next" for me:

I tried a git am on my for-4.21 and for-next branches and it didn't work
on either, I didn't investigate beyond that.

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