From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Venu Byravarasu <vbyravarasu@nvidia.com>
Cc: "lrg@ti.com" <lrg@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: Add TPS65090 regulator driver
Date: Thu, 22 Mar 2012 11:20:34 +0000 [thread overview]
Message-ID: <20120322112033.GB3091@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <D958900912E20642BCBC71664EFECE3E6DD3127F90@BGMAIL02.nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
On Thu, Mar 22, 2012 at 11:35:24AM +0530, Venu Byravarasu wrote:
> As the MFD got merged in linux-next, can you please review the regulator
> driver patch I sent.
Two things:
- Never top post.
- You appear to be replying to my review...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-22 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 7:35 [PATCH] regulator: Add TPS65090 regulator driver Venu Byravarasu
2012-03-21 8:51 ` Mark Brown
2012-03-22 6:05 ` Venu Byravarasu
2012-03-22 11:20 ` Mark Brown [this message]
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=20120322112033.GB3091@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=vbyravarasu@nvidia.com \
/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