From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] Device tree support for TWL regulators
Date: Tue, 28 Feb 2012 10:18:50 +0000 [thread overview]
Message-ID: <20120228101850.GA3121@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F4C691C.2000600@ti.com>
On Tue, Feb 28, 2012 at 11:11:48AM +0530, Rajendra Nayak wrote:
> 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.
Yes, that sounds like a good plan - the DTS changes are largely
orthogonal to the code changes and don't need to go via the same path
(this is true in general, the DTSs are pretty horrible for merge
issues).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120228/b1bcadfe/attachment.sig>
next prev parent reply other threads:[~2012-02-28 10:18 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
2012-02-28 10:18 ` Mark Brown [this message]
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=20120228101850.GA3121@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).