From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"lrg@ti.com" <lrg@ti.com>
Subject: Re: [PATCH 2/2] regulator: palmas: add input supply names
Date: Wed, 20 Mar 2013 10:07:17 -0600 [thread overview]
Message-ID: <5149DEB5.7000709@wwwdotorg.org> (raw)
In-Reply-To: <5149B19E.90400@nvidia.com>
On 03/20/2013 06:54 AM, Laxman Dewangan wrote:
> On Wednesday 20 March 2013 06:01 PM, Mark Brown wrote:
>> * PGP Signed by an unknown key
>>
>> On Mon, Mar 18, 2013 at 02:59:48PM +0530, Laxman Dewangan wrote:
>>
>> There's something odd about several recent patch serieses you've posted,
>> they end up with patch 2 before instead of after patch 1. Anyway...
>
> I generally send a patches on single git-send command
> git send-emal --to=ldewangan@nvidia.com 0000.patch 0001.patch
Don't do that; send *.patch. If you don't, then patches 2..n don't end
up being "in-reply-to" patch 1, so they won't show up as a single email
thread.
next prev parent reply other threads:[~2013-03-20 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 9:29 [PATCH 2/2] regulator: palmas: add input supply names Laxman Dewangan
2013-03-18 9:29 ` [PATCH 1/2] regulator: palmas: rename probe/remove callback functions Laxman Dewangan
[not found] ` <20130320123128.GM28775@opensource.wolfsonmicro.com>
2013-03-20 12:54 ` [PATCH 2/2] regulator: palmas: add input supply names Laxman Dewangan
[not found] ` <20130320132531.GO28775@opensource.wolfsonmicro.com>
2013-03-20 13:32 ` Laxman Dewangan
2013-03-20 16:07 ` Stephen Warren [this message]
[not found] ` <20130320163833.GT28775@opensource.wolfsonmicro.com>
2013-03-20 16:42 ` Stephen Warren
[not found] ` <20130320165227.GU28775@opensource.wolfsonmicro.com>
2013-03-20 16:56 ` Stephen Warren
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=5149DEB5.7000709@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@ti.com \
--cc=swarren@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