From: Stephen Warren <swarren@wwwdotorg.org>
To: Liam Girdwood <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Samuel Ortiz <sameo@linux.intel.com>
Cc: 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: [PATCH 0/4] deprecate regulator-compatible DT property
Date: Mon, 24 Sep 2012 13:24:59 -0600 [thread overview]
Message-ID: <1348514703-10152-1-git-send-email-swarren@wwwdotorg.org> (raw)
From: Stephen Warren <swarren@nvidia.com>
As explained in patch 1, this series deprecates the regulator-compatible
DT property, and updates various binding documentation and examples for
this change.
I expect patches 1-3 to go into various regulator topic trees, and patch
4 to go into the MFD tree.
Stephen Warren (4):
regulator: deprecate regulator-compatible DT property
regulator: tps65217.txt: remove regulator-compatible from DT docs
regulator: tps6586x: remove regulator-compatible from DT docs
mfd: max8907: remove regulator-compatible from DT docs
.../devicetree/bindings/regulator/max8907.txt | 24 +++-----
.../devicetree/bindings/regulator/regulator.txt | 5 +-
.../devicetree/bindings/regulator/tps65217.txt | 31 ++-------
.../devicetree/bindings/regulator/tps6586x.txt | 66 ++++++--------------
drivers/regulator/of_regulator.c | 25 ++++----
5 files changed, 50 insertions(+), 101 deletions(-)
next reply other threads:[~2012-09-24 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 19:24 Stephen Warren [this message]
2012-09-24 19:25 ` [PATCH 1/4] regulator: " Stephen Warren
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
2012-09-25 12:46 ` [PATCH 0/4] deprecate regulator-compatible DT property 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=1348514703-10152-1-git-send-email-swarren@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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=sameo@linux.intel.com \
--cc=swarren@nvidia.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
all inboxes | Powered by JetHome®