From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
lrg@ti.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: tps6586x: correct vin pin for sm0/sm1/sm2
Date: Thu, 9 Aug 2012 19:11:06 +0100 [thread overview]
Message-ID: <20120809181106.GA24328@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5023FCDB.4080607@wwwdotorg.org>
On Thu, Aug 09, 2012 at 12:09:31PM -0600, Stephen Warren wrote:
> The patch in question just showed up again in next-20120809:
> 7f852e0 regulator: tps6586x: correct vin pin for sm0/sm1/sm2
> ... with the exact same content as the previous commit ID.
Oh, in that case I must've missed a branch when I was rebuilding -next.
I just checked for missing branches. Problem solved.
prev parent reply other threads:[~2012-08-09 18:11 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
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 [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=20120809181106.GA24328@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.