From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] regulator: twl: adapt twl-regulator driver to dt
Date: Tue, 20 Dec 2011 01:03:52 +0000 [thread overview]
Message-ID: <20111220010351.GP2860@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1323771575-3550-2-git-send-email-rnayak@ti.com>
On Tue, Dec 13, 2011 at 03:49:33PM +0530, Rajendra Nayak wrote:
I'm OK with this but would prefer that OMAP or TWL people were OK with
it too. If you do need to respin:
> +For twl4030 regulators/LDO's
' should *not* be used for plurals except when omitting a duplicated s
introduced by one (grammar nit but it really bugs me).
next prev parent reply other threads:[~2011-12-20 1:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 10:19 [PATCH v2 0/3] Device tree support for TWL regulators Rajendra Nayak
2011-12-13 10:19 ` [PATCH v2 1/3] regulator: twl: adapt twl-regulator driver to dt Rajendra Nayak
2011-12-20 1:03 ` Mark Brown [this message]
2011-12-13 10:19 ` [PATCH v2 2/3] ARM: omap4-sdp: Pass regulator data from dt Rajendra Nayak
2011-12-13 10:19 ` [PATCH v2 3/3] omap4: panda: " 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=20111220010351.GP2860@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).