From: Mark Brown <broonie@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: David Collins <collinsd@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Stephen Boyd <sboyd@kernel.org>,
Matthias Kaehlcke <mka@chromium.org>,
Andy Gross <andy.gross@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH v8 2/2] regulator: add QCOM RPMh regulator driver
Date: Wed, 27 Jun 2018 16:01:26 +0100 [thread overview]
Message-ID: <20180627150126.GC5263@sirena.org.uk> (raw)
In-Reply-To: <CAD=FV=WC_XWRk-6OELOFFWGnhRq1VeoiiveqXLSy+xqsVb22pA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On Tue, Jun 26, 2018 at 11:15:14AM -0700, Doug Anderson wrote:
> I think he's still planning on re-shuffling his tree a bit. When he
> does this, do you need him to put the RPMh patches somewhere you can
> merge into your tree?
Well, I *think* there's no actual dependency here since it's a new
driver with a Kconfig dependency. It really just needs me to get round
to trawling through what's a fairly large patch with a troubled history
now you've reviewed it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-06-27 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 0:46 [PATCH v8 0/2] " David Collins
2018-06-23 0:46 ` [PATCH v8 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings David Collins
2018-06-23 0:46 ` [PATCH v8 2/2] regulator: add QCOM RPMh regulator driver David Collins
2018-06-25 18:50 ` Doug Anderson
2018-06-26 12:07 ` Mark Brown
2018-06-26 15:00 ` Doug Anderson
2018-06-26 15:02 ` Mark Brown
2018-06-26 18:15 ` Doug Anderson
2018-06-27 15:01 ` Mark Brown [this message]
2018-06-27 16:28 ` Doug Anderson
2018-06-28 10:18 ` Mark Brown
2018-06-28 18:04 ` David Collins
2018-06-29 11:06 ` Mark Brown
2018-07-02 10:28 ` Mark Brown
2018-07-09 23:44 ` David Collins
2018-07-12 16:54 ` Mark Brown
2018-07-13 1:34 ` David Collins
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=20180627150126.GC5263@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=collinsd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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
all inboxes | Powered by JetHome®