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 <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>
Subject: Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings
Date: Tue, 24 Jul 2018 16:25:14 +0100 [thread overview]
Message-ID: <20180724152514.GJ13268@sirena.org.uk> (raw)
In-Reply-To: <CAD=FV=Uo8sT72a0gRitOVoK0SfC-_QixsovW94_LnL6H7QdKvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On Tue, Jul 24, 2018 at 08:11:30AM -0700, Doug Anderson wrote:
> RPMh itself landed in Andy's tree and he sent a pull request on
> Saturday. Feel free to refer to the request ("[GIT PULL] Qualcomm
> Driver updates for 4.19") AKA
> <https://patchwork.kernel.org/patch/10539125/>.
> It doesn't look like arm-soc has picked up Andy's pull request yet
> though. If having it in arm-soc is a requirement then I'm happy to
> monitor arm-soc and ping this thread again when it's there.
There was also some other thing called command DB as well which was a
separate series. Ideally there'd be a branch I could pull as there's a
build dependency on rpmh so I can't apply until the code has landed in
my tree, don't know what command DB is exactly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-24 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 1:50 [PATCH v9 0/2] regulator: add QCOM RPMh regulator driver David Collins
2018-07-14 1:50 ` [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings David Collins
2018-07-23 20:09 ` Doug Anderson
2018-07-24 14:57 ` Mark Brown
2018-07-24 15:11 ` Doug Anderson
2018-07-24 15:25 ` Mark Brown [this message]
2018-07-24 15:43 ` Doug Anderson
2018-07-24 16:59 ` Mark Brown
2018-07-26 18:39 ` Andy Gross
2018-08-06 22:55 ` Doug Anderson
2018-08-06 23:55 ` Mark Brown
2018-07-14 1:50 ` [PATCH v9 2/2] regulator: add QCOM RPMh regulator driver David Collins
2018-08-10 16:29 ` Mark Brown
2018-08-10 20:07 ` 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=20180724152514.GJ13268@sirena.org.uk \
--to=broonie@kernel.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®