linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Dmitry Osipenko <digetx@gmail.com>,
	Evan Green <evgreen@chromium.org>,
	masneyb@onstation.org, Liam Girdwood <lgirdwood@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: core: Clean enabling always-on regulators + their supplies
Date: Mon, 10 Dec 2018 08:32:32 -0800	[thread overview]
Message-ID: <CAD=FV=X33+-TiBohnwN6+2R26iwxW0Rcthp16-3XYy+01hW4nw@mail.gmail.com> (raw)
In-Reply-To: <20181210154311.GF6307@sirena.org.uk>

Mark,

On Mon, Dec 10, 2018 at 7:43 AM Mark Brown <broonie@kernel.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

  reply	other threads:[~2018-12-10 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 22:23 [PATCH] regulator: core: Clean enabling always-on regulators + their supplies Douglas Anderson
2018-12-07  1:31 ` Brian Masney
2018-12-10 15:43 ` Mark Brown
2018-12-10 16:32   ` Doug Anderson [this message]
2018-12-11  0:52     ` Mark Brown
2018-12-11  1:00       ` Mark Brown
2018-12-11  2:40         ` Doug Anderson
2018-12-11 14:06           ` Mark Brown
2018-12-11 16:21             ` Doug Anderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAD=FV=X33+-TiBohnwN6+2R26iwxW0Rcthp16-3XYy+01hW4nw@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=broonie@kernel.org \
    --cc=digetx@gmail.com \
    --cc=evgreen@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masneyb@onstation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).