public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jim Baxter <jim_baxter@mentor•com>
To: David Miller <davem@davemloft•net>
Cc: <netdev@vger•kernel.org>
Subject: Re: [PATCH net-next v2 1/1] net: fec: Enable imx6 enet checksum acceleration.
Date: Tue, 16 Apr 2013 23:16:22 +0100	[thread overview]
Message-ID: <516DCDB6.4050405@mentor.com> (raw)
In-Reply-To: <20130416.140032.376392714783850324.davem@davemloft.net>

On 16/04/13 19:00, David Miller wrote:
> From: Jim Baxter <jim_baxter@mentor•com>
> Date: Tue, 16 Apr 2013 14:09:25 +0000 (UTC)
> 
>> David Miller <davem <at> davemloft.net> writes:
>>
>>>
>>>
>>> When you post multiple versions of a patch, always say what is different
>>> between the versions.
>>>
>>
>>
>> Sorry, I was trying to differentiate between my first two messed up posts and 
>> the correct patch post. I first forgot to mark it net-net and then I managed 
>> to send it from y@relay1•mentorg.com.
>>
>> Is there a better way to correct incorrect patch headers?
> 
> You post it again, but you say what you changed so that we know what
> is happening.
> 
> You put such change annotations after the "---" seperator so that they
> do not appear in the final commit message.
> 

OK, Thank you for your help.

Jim

  reply	other threads:[~2013-04-16 22:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 10:36 [PATCH net-next v2 1/1] net: fec: Enable imx6 enet checksum acceleration Jim Baxter
2013-04-16 12:35 ` David Miller
2013-04-16 14:09   ` Jim Baxter
2013-04-16 18:00     ` David Miller
2013-04-16 22:16       ` Jim Baxter [this message]
2013-04-16 13:50 ` Eric Dumazet
2013-04-16 15:30   ` Jim Baxter
2013-04-16 15:39 ` Ben Hutchings
2013-04-16 22:15   ` Jim Baxter
2013-04-16 22:41     ` Ben Hutchings
2013-04-17 14:43       ` Jim Baxter

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=516DCDB6.4050405@mentor.com \
    --to=jim_baxter@mentor$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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