From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/3] regulator: qcom-rpm: Regulator driver for the Qualcomm RPM
Date: Wed, 16 Jul 2014 23:30:10 +0100 [thread overview]
Message-ID: <20140716223010.GP17528@sirena.org.uk> (raw)
In-Reply-To: <CAJAp7OjzWw6uBVsMXEvx0Lc1v_UJ+hGa2UeaQCtdfzsm+nAMDQ@mail.gmail.com>
On Wed, Jul 16, 2014 at 03:15:16PM -0700, Bjorn Andersson wrote:
> On Tue, Jul 15, 2014 at 5:08 PM, Mark Brown <broonie@kernel.org> wrote:
> > I have patch 3/3 here but no cover or other patches - what is the story
> > there?
> I forgot to add you as explicit recipient of the other mails in the
> series, sorry about that. Please let me know if you would like to have
> them resent.
I mostly want to know about the dependencies - I guess the first couple
of patches define the QCOM_RPM interface, is that stable enough to go
ahead with the regulator driver for example?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140716/2e854a0e/attachment-0001.sig>
next prev parent reply other threads:[~2014-07-16 22:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 23:00 [PATCH v4 0/3] Qualcomm Resource Power Manager driver Bjorn Andersson
2014-07-15 23:00 ` [PATCH v4 1/3] soc: devicetree: bindings: Add Qualcomm RPM DT binding Bjorn Andersson
2014-07-16 10:06 ` pramod gurav
2014-07-16 22:20 ` Bjorn Andersson
2014-07-17 16:04 ` pramod gurav
2014-07-15 23:00 ` [PATCH v4 2/3] soc: qcom-rpm: Driver for the Qualcomm RPM Bjorn Andersson
2014-07-17 17:33 ` pramod gurav
2014-07-17 18:17 ` Bjorn Andersson
2014-07-15 23:00 ` [PATCH v4 3/3] regulator: qcom-rpm: Regulator driver " Bjorn Andersson
2014-07-16 0:08 ` Mark Brown
2014-07-16 22:15 ` Bjorn Andersson
2014-07-16 22:30 ` Mark Brown [this message]
2014-07-16 7:01 ` pramod gurav
2014-07-16 22:17 ` Bjorn Andersson
2014-07-16 22:28 ` Mark Brown
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=20140716223010.GP17528@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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