[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=X33+-TiBohnwN6+2R26iwxW0Rcthp16-3XYy+01hW4nw@mail.gmail.com>
Date: Mon, 10 Dec 2018 08:32:32 -0800
From: Doug Anderson <dianders@...omium.org>
To: Mark Brown <broonie@...nel.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
Mark,
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:
$ git remote -v | grep linuxregulator
linuxregulator
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
(fetch)
linuxregulator
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
(push)
$ git fetch linuxregulator
$ git log --oneline -1 linuxregulator/for-next
f00e93a1224f (linuxregulator/for-next) Merge remote-tracking branch
'regulator/topic/coupled' into regulator-next
$ git checkout linuxregulator/for-next
[ ... cut ... ]
HEAD is now at f00e93a1224f Merge remote-tracking branch
'regulator/topic/coupled' into regulator-next
$ pwclient git-am -p lkml 1022439
Applying patch #1022439 using u'git am'
Description: regulator: core: Clean enabling always-on regulators +
their supplies
Applying: regulator: core: Clean enabling always-on regulators + their supplies
Thanks!
-Doug
Powered by blists - more mailing lists