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: Mon, 27 Feb 2012 13:41:12 +0000 [thread overview]
Message-ID: <20120227134112.GB3191@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F4B7798.6000300@ti.com>
On Mon, Feb 27, 2012 at 06:01:20PM +0530, Rajendra Nayak wrote:
> Depending on what order Mark happens to pull them in, I am fine
> re-sending adding support for the 2 twl6030 fixed regulators.
Please can you guys come up with a single unified series for this stuff
- I'll hold off on applying anything to allow you to do 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/20120227/b24942a0/attachment.sig>
next prev parent reply other threads:[~2012-02-27 13: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 [this message]
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
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=20120227134112.GB3191@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).