From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: lrg@ti.com, swarren@wwwdotorg.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: tps6586x: correct vin pin for sm0/sm1/sm2
Date: Wed, 1 Aug 2012 21:06:46 +0100 [thread overview]
Message-ID: <20120801200646.GR4483@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1343117880-11576-1-git-send-email-ldewangan@nvidia.com>
On Tue, Jul 24, 2012 at 01:48:00PM +0530, Laxman Dewangan wrote:
> As per datasheet, the vin pin for the regulator is named
> as vin_sm0, vin_sm1, vin_sm2 for sm0, sm1 and sm2 respectively.
Applied, thanks.
next prev parent reply other threads:[~2012-08-01 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 8:18 [PATCH] regulator: tps6586x: correct vin pin for sm0/sm1/sm2 Laxman Dewangan
2012-07-24 16:00 ` Stephen Warren
2012-08-01 20:06 ` Mark Brown [this message]
2012-08-08 21:57 ` Stephen Warren
2012-08-09 18:05 ` Mark Brown
2012-08-09 18:09 ` Stephen Warren
2012-08-09 18:11 ` Mark Brown
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=20120801200646.GR4483@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=swarren@wwwdotorg.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).