From: Mark Brown Subject: Re: [PATCH] regulator: core: Clean enabling always-on regulators + their supplies Date: Tue, 11 Dec 2018 00:52:21 +0000 Message-ID: <20181211005221.GB3004@sirena.org.uk> References: <20181206222318.240401-1-dianders@chromium.org> <20181210154311.GF6307@sirena.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GRPZ8SYKNexpdSJ7" Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Doug Anderson Cc: linux-arm-msm , Dmitry Osipenko , Evan Green , masneyb@onstation.org, Liam Girdwood , LKML List-Id: linux-arm-msm@vger.kernel.org --GRPZ8SYKNexpdSJ7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Dec 10, 2018 at 08:32:32AM -0800, Doug Anderson wrote: > On Mon, Dec 10, 2018 at 7:43 AM Mark Brown 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. --GRPZ8SYKNexpdSJ7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlwPCkQACgkQJNaLcl1U h9B06wf9EpiWzf29xBmmhqd79v5rJetc45FV8S/Phs/qOd/rUp8tRe4oppsWeqAl eaqLc+RS0xtJ0ybsysWjUXy/RS7Eb/m0DZmjPSRdWHOnDntQ3DpRfELSMcJgWsiV JylGviGJ8Y06hF/RjX29sArtQKOuYk5j6FazjcVpy3U40jXLZ+qdyMsHIJlZqXuF UzbDuL6i5rtvkmblqftVbv54FkQgyo5mnUKmEFBo/vxiWjPmlhepximIPooJv6vW 1RVoMdIt6UJMBHcTxy3pPDhpxcpQjH8KiKAL7YtaOfyZAg/i2tq4GBuViCM4/D4P pw3td3Dnh8LKcqkTJfASeMlZVLOW0A== =kDpS -----END PGP SIGNATURE----- --GRPZ8SYKNexpdSJ7--