From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 1/2] regulator: Add document for MT6323 regulator
Date: Mon, 8 Feb 2016 15:24:43 -0600 [thread overview]
Message-ID: <20160208212443.GA32296@rob-hp-laptop> (raw)
In-Reply-To: <1454874037-38905-1-git-send-email-blogic@openwrt.org>
On Sun, Feb 07, 2016 at 08:40:36PM +0100, John Crispin wrote:
> Signed-off-by: John Crispin <blogic@openwrt.org>
> Cc: devicetree at vger.kernel.org
>
> ---
> Changes in V5
> * regulator vs regulators
>
> Changes in V4
> * regulator is a subnode and not a property
>
> .../bindings/regulator/mt6323-regulator.txt | 244 ++++++++++++++++++++
> 1 file changed, 244 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/mt6323-regulator.txt
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-02-08 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 19:40 [PATCH V5 1/2] regulator: Add document for MT6323 regulator John Crispin
2016-02-07 19:40 ` [PATCH V5 2/2] regulator: mt6323: Add support " John Crispin
2016-02-09 12:36 ` Mark Brown
2016-02-08 21:24 ` Rob Herring [this message]
2016-02-09 12:41 ` [PATCH V5 1/2] regulator: Add document " Mark Brown
2016-02-09 12:45 ` John Crispin
2016-02-09 15:17 ` 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=20160208212443.GA32296@rob-hp-laptop \
--to=robh@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