All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] omap2plus: Trivial build break fixes
Date: Wed, 05 Jan 2011 09:20:00 -0800	[thread overview]
Message-ID: <87r5crz2rj.fsf@ti.com> (raw)
In-Reply-To: <6a39d0124306a5ac6b567edca88f0671@mail.gmail.com> (Santosh Shilimkar's message of "Wed, 5 Jan 2011 16:28:47 +0530")

Santosh Shilimkar <santosh.shilimkar@ti.com> writes:

[...]

>> Minor nit in your git-send-email config.
>>
>> Can you add the following to your ~/.gitconfig, or update to newer
>> git
>> where this is now the default:
>>
>> [sendemail]
>> 	chainreplyto = false
>>
>> This will make all patches a reply to PATCH 0 instead of to the
>> previous
>> patch.
>>
> Have tried this in v2 I posted but it didn't appear to be a
> reply for PATCH 0.

You didn't have (or I didn't see) a PATCH 0 in your v2 version.  After
patch 1, all patches are replies to patch 1 (using In-Reply-To: and
References:) resulting in proper threading.

> May be I missed something.

I don't think so, it looks right now.

Kevin



WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] omap2plus: Trivial build break fixes
Date: Wed, 05 Jan 2011 09:20:00 -0800	[thread overview]
Message-ID: <87r5crz2rj.fsf@ti.com> (raw)
In-Reply-To: <6a39d0124306a5ac6b567edca88f0671@mail.gmail.com> (Santosh Shilimkar's message of "Wed, 5 Jan 2011 16:28:47 +0530")

Santosh Shilimkar <santosh.shilimkar@ti.com> writes:

[...]

>> Minor nit in your git-send-email config.
>>
>> Can you add the following to your ~/.gitconfig, or update to newer
>> git
>> where this is now the default:
>>
>> [sendemail]
>> 	chainreplyto = false
>>
>> This will make all patches a reply to PATCH 0 instead of to the
>> previous
>> patch.
>>
> Have tried this in v2 I posted but it didn't appear to be a
> reply for PATCH 0.

You didn't have (or I didn't see) a PATCH 0 in your v2 version.  After
patch 1, all patches are replies to patch 1 (using In-Reply-To: and
References:) resulting in proper threading.

> May be I missed something.

I don't think so, it looks right now.

Kevin

  reply	other threads:[~2011-01-05 17:20 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 18:26 [PATCH 0/5] omap2plus: Trivial build break fixes Santosh Shilimkar
2011-01-04 18:26 ` Santosh Shilimkar
2011-01-04 18:26 ` [PATCH 1/5] omap2plus: clockdomain: Trivial fix for build break because of clktrctrl_mask Santosh Shilimkar
2011-01-04 18:26   ` Santosh Shilimkar
2011-01-04 18:26   ` [PATCH 2/5] omap2plus: prm: Trvial build break fix for undefined reference to 'omap2_prm_read_mod_reg' Santosh Shilimkar
2011-01-04 18:26     ` Santosh Shilimkar
2011-01-04 18:26     ` [PATCH 3/5] omap2plus: voltage: Trivial warning fix 'no return statement' Santosh Shilimkar
2011-01-04 18:26       ` Santosh Shilimkar
2011-01-04 18:26       ` [PATCH 4/5] omap2plus: voltage: Trivial linking fix 'undefined reference' Santosh Shilimkar
2011-01-04 18:26         ` Santosh Shilimkar
2011-01-04 18:26         ` [PATCH 5/5] omap2plus: voltage: Trivial linking fix for 'EINVAL' undeclared Santosh Shilimkar
2011-01-04 18:26           ` Santosh Shilimkar
2011-01-04 18:49           ` Nishanth Menon
2011-01-04 18:49             ` Nishanth Menon
2011-01-04 18:51             ` Santosh Shilimkar
2011-01-04 18:51               ` Santosh Shilimkar
2011-01-04 18:56               ` Nishanth Menon
2011-01-04 18:56                 ` Nishanth Menon
2011-01-04 18:46         ` [PATCH 4/5] omap2plus: voltage: Trivial linking fix 'undefined reference' Nishanth Menon
2011-01-04 18:46           ` Nishanth Menon
2011-01-04 18:48           ` Santosh Shilimkar
2011-01-04 18:48             ` Santosh Shilimkar
2011-01-04 18:50             ` Santosh Shilimkar
2011-01-04 18:50               ` Santosh Shilimkar
2011-01-04 18:52               ` Nishanth Menon
2011-01-04 18:52                 ` Nishanth Menon
2011-01-04 18:43       ` [PATCH 3/5] omap2plus: voltage: Trivial warning fix 'no return statement' Nishanth Menon
2011-01-04 18:43         ` Nishanth Menon
2011-01-04 18:46         ` Santosh Shilimkar
2011-01-04 18:46           ` Santosh Shilimkar
2011-01-04 18:41     ` [PATCH 2/5] omap2plus: prm: Trvial build break fix for undefined reference to 'omap2_prm_read_mod_reg' Paul Walmsley
2011-01-04 18:41       ` Paul Walmsley
2011-01-04 18:43       ` Santosh Shilimkar
2011-01-04 18:43         ` Santosh Shilimkar
2011-01-05  0:32         ` Kevin Hilman
2011-01-05  0:32           ` Kevin Hilman
2011-01-05  8:18           ` Santosh Shilimkar
2011-01-05  8:18             ` Santosh Shilimkar
2011-01-04 18:43   ` [PATCH 1/5] omap2plus: clockdomain: Trivial fix for build break because of clktrctrl_mask Paul Walmsley
2011-01-04 18:43     ` Paul Walmsley
2011-01-04 18:45     ` Santosh Shilimkar
2011-01-04 18:45       ` Santosh Shilimkar
2011-01-05  0:37 ` [PATCH 0/5] omap2plus: Trivial build break fixes Kevin Hilman
2011-01-05  0:37   ` Kevin Hilman
2011-01-05 10:58   ` Santosh Shilimkar
2011-01-05 10:58     ` Santosh Shilimkar
2011-01-05 17:20     ` Kevin Hilman [this message]
2011-01-05 17:20       ` Kevin Hilman

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=87r5crz2rj.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.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 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.