From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] regulator: twl: adapt twl-regulator driver to dt
Date: Thu, 23 Feb 2012 15:31:27 +0000 [thread overview]
Message-ID: <20120223153127.GD4553@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1329996954-27083-2-git-send-email-rnayak@ti.com>
On Thu, Feb 23, 2012 at 05:05:53PM +0530, Rajendra Nayak wrote:
> Modify the twl regulator driver to extract the regulator_init_data from
> device tree when passed, instead of getting it through platform_data
> structures (on non-DT builds)
This doesn't apply to current -next, I expect because of the SMPS
regulator changes which went in. Please always submit patches against
-next. There's also a patch from Tero adding support for some
additional regulators which is floating around and would conflict with
this. Could you guys please coordinate with each other on this?
-------------- 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/20120223/e2644df1/attachment.sig>
next prev parent reply other threads:[~2012-02-23 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 11:35 [PATCH v3 0/2] Device tree support for TWL regulators Rajendra Nayak
2012-02-23 11:35 ` [PATCH v3 1/2] regulator: twl: adapt twl-regulator driver to dt Rajendra Nayak
2012-02-23 15:31 ` Mark Brown [this message]
2012-02-24 3:48 ` Rajendra Nayak
2012-02-23 11:35 ` [PATCH v3 2/2] arm/dts: twl: Pass regulator data from dt Rajendra Nayak
-- strict thread matches above, loose matches on Subject: below --
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
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=20120223153127.GD4553@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).