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 15:57:55 +0100 [thread overview]
Message-ID: <20180724145755.GF13268@sirena.org.uk> (raw)
In-Reply-To: <CAD=FV=VmfqWRGRMEn+0dzZ8x4R5vVaHbkthXAN91Lm-XmP9Gqg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On Mon, Jul 23, 2018 at 01:09:05PM -0700, Doug Anderson wrote:
> I know you are still looking for time to review the RPMh-regulator
> driver and that's fine. One idea I had though: if the bindings look
> OK to you and are less controversial, is there any chance they could
> land in the meantime?
This appears to have a bunch of dependencies which I've got no idea
what's going on with the merging of and no idea if they'll affect the
bindings or anything, nobody's said anything and last I looked it was
unclear what was going on. I'm kind of hoping that things might have
sorted themselves out of the merge window.
Some of the decisions in the code have flowed out into the bindings
before so I'm not keen to merge the bindings separately, and if the
driver for the thing used to communicate with the device is still in
review then that's definitely a red flag.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-24 14:58 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 [this message]
2018-07-24 15:11 ` Doug Anderson
2018-07-24 15:25 ` Mark Brown
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=20180724145755.GF13268@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
Powered by JetHome