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: <20181211140609.GD6686@sirena.org.uk>
Date:   Tue, 11 Dec 2018 14:06:09 +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 06:40:53PM -0800, Doug Anderson wrote:

> Can you confirm my patch applies cleanly to your for-next branch?  I
> can see that it doesn't apply to your 4.21 branch but I can't see it
> fail on your for-next branch.

No, I tried both and it didn't work on either.

> The problem is that commit 2bb166636933 ("regulator: core: enable
> power when setting up constraints") touches the same code but isn't in
> the 4.21 branch.  If you pick that to your 4.21 then my patch applies
> cleanly.

> If you'd prefer that I post my patch atop 4.21 I can do that tomorrow.

I'd prefer that you resend like I said :(

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