From: Rob Herring <robh@kernel.org>
To: Saravanan Sekar <sravanhome@gmail.com>
Cc: sravanhome@gmail.com, lgirdwood@gmail.com, broonie@kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
gregkh@linuxfoundation.org, Jonathan.Cameron@huawei.com,
davem@davemloft.net, mchehab+samsung@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: regulator: add document bindings for mp5416
Date: Thu, 6 Feb 2020 19:10:57 +0000 [thread overview]
Message-ID: <20200206191057.GA19653@bogus> (raw)
In-Reply-To: <20200204110419.25933-2-sravanhome@gmail.com>
On Tue, 4 Feb 2020 12:04:17 +0100, Saravanan Sekar wrote:
> Add device tree binding information for mp5416 regulator driver.
>
> Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
> ---
> .../bindings/regulator/mps,mp5416.yaml | 78 +++++++++++++++++++
> 1 file changed, 78 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/mps,mp5416.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-02-06 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 11:04 [PATCH v2 0/3] Add regulator support for mpq5416 Saravanan Sekar
2020-02-04 11:04 ` [PATCH v2 1/3] dt-bindings: regulator: add document bindings for mp5416 Saravanan Sekar
2020-02-06 19:10 ` Rob Herring [this message]
2020-02-11 15:51 ` Applied "dt-bindings: regulator: add document bindings for mp5416" to the regulator tree Mark Brown
2020-02-04 11:04 ` [PATCH v2 2/3] regulator: mp5416: add mp5416 regulator driver Saravanan Sekar
2020-02-11 15:51 ` Applied "regulator: mp5416: add mp5416 regulator driver" to the regulator tree Mark Brown
2020-02-04 11:04 ` [PATCH v2 3/3] MAINTAINERS: Add entry for mp5416 PMIC driver Saravanan Sekar
2020-02-11 15:51 ` Applied "MAINTAINERS: Add entry for mp5416 PMIC driver" to the regulator tree 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=20200206191057.GA19653@bogus \
--to=robh@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sravanhome@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).