From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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, 09 Aug 2012 12:09:31 -0600 [thread overview]
Message-ID: <5023FCDB.4080607@wwwdotorg.org> (raw)
In-Reply-To: <20120809180514.GZ24328@opensource.wolfsonmicro.com>
On 08/09/2012 12:05 PM, Mark Brown wrote:
> On Wed, Aug 08, 2012 at 03:57:04PM -0600, Stephen Warren wrote:
>
>> I assume that was just an accident?
>
> Probably. I suspect a conflict with mainline when I rebased onto
> v3.6-rc1. Please resend the patch, I don't think I have it any more.
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.
next prev parent reply other threads:[~2012-08-09 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 8:18 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 [this message]
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=5023FCDB.4080607@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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
Powered by JetHome