From: Samuel Ortiz <sameo@linux.intel.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Liam Girdwood <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>,
Laxman Dewangan <ldewangan@nvidia.com>,
AnilKumar Ch <anilkumar@ti.com>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH 4/4] mfd: max8907: remove regulator-compatible from DT docs
Date: Tue, 25 Sep 2012 15:22:12 +0200 [thread overview]
Message-ID: <20120925132212.GO28670@sortiz-mobl> (raw)
In-Reply-To: <1348514703-10152-5-git-send-email-swarren@wwwdotorg.org>
Hi Stephen,
On Mon, Sep 24, 2012 at 01:25:03PM -0600, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Commit "regulator: deprecate regulator-compatible DT property" deprecated
> the use of the regulator-compatible DT property. Update the DT example in
> the MAX8907 binding documentation to reflect this.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> This commit is based on the MFD branch.
> ---
> .../devicetree/bindings/regulator/max8907.txt | 24 ++++++-------------
> 1 files changed, 8 insertions(+), 16 deletions(-)
Applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-09-25 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 19:24 [PATCH 0/4] deprecate regulator-compatible DT property Stephen Warren
[not found] ` <1348514703-10152-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-09-24 19:25 ` [PATCH 1/4] regulator: " Stephen Warren
2012-09-25 12:46 ` [PATCH 0/4] " Mark Brown
2012-09-24 19:25 ` [PATCH 2/4] regulator: tps65217.txt: remove regulator-compatible from DT docs Stephen Warren
2012-09-24 19:25 ` [PATCH 3/4] regulator: tps6586x: " Stephen Warren
2012-09-24 19:25 ` [PATCH 4/4] mfd: max8907: " Stephen Warren
2012-09-25 13:22 ` Samuel Ortiz [this message]
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=20120925132212.GO28670@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=anilkumar@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).