From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] Device tree support for TWL regulators
Date: Tue, 28 Feb 2012 11:11:48 +0530 [thread overview]
Message-ID: <4F4C691C.2000600@ti.com> (raw)
In-Reply-To: <20120227145345.GJ3191@opensource.wolfsonmicro.com>
On Monday 27 February 2012 08:23 PM, Mark Brown wrote:
> If adding device tree support breaks existing platforms something is
> going wrong, while you're pulling things together device tree might not
> work until all the support makes it in but the old non-DT code should
> continue to function.
Adding device tree support will not break existing platforms. The
non-DT code will function as expected. The dependencies I mentioned
were only with the dtsi/dts files that patch 2 was updating. The driver
changes have no dependencies with any other DT series. I will repost
all of Tero/Peter and my changes (to add DT support to the driver) as
one single series and drop the dts file updates, which I guess can go
via Tony/OMAP tree.
>
next prev parent reply other threads:[~2012-02-28 5:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 10:35 [PATCH v3 0/2] Device tree support for TWL regulators Rajendra Nayak
2012-02-27 10:36 ` [PATCH v3 1/2] regulator: twl: adapt twl-regulator driver to dt Rajendra Nayak
2012-02-27 10:36 ` [PATCH v3 2/2] arm/dts: twl: Pass regulator data from dt Rajendra Nayak
2012-02-27 12:15 ` [PATCH v3 0/2] Device tree support for TWL regulators Peter Ujfalusi
2012-02-27 12:31 ` Rajendra Nayak
2012-02-27 13:41 ` Mark Brown
2012-02-27 13:52 ` Cousson, Benoit
2012-02-27 14:03 ` Mark Brown
2012-02-27 14:21 ` Cousson, Benoit
2012-02-27 14:53 ` Mark Brown
2012-02-28 5:41 ` Rajendra Nayak [this message]
2012-02-28 10:18 ` Mark Brown
2012-02-27 22:17 ` Grant Likely
2012-02-27 22:24 ` Cousson, Benoit
-- strict thread matches above, loose matches on Subject: below --
2012-02-23 11:35 Rajendra Nayak
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=4F4C691C.2000600@ti.com \
--to=rnayak@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).