From: David Daney <ddaney@caviumnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: <ddaney.cavm@gmail.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <rric@kernel.org>,
<sgoutham@cavium.com>, <david.daney@cavium.com>
Subject: Re: [PATCH] net: thunderx: Fix broken of_node_put() code.
Date: Fri, 8 Apr 2016 13:34:26 -0700 [thread overview]
Message-ID: <570815D2.5050608@caviumnetworks.com> (raw)
In-Reply-To: <20160408.161557.850174112269792582.davem@davemloft.net>
On 04/08/2016 01:15 PM, David Miller wrote:
> From: David Daney <ddaney@caviumnetworks.com>
> Date: Fri, 8 Apr 2016 09:41:35 -0700
>
>> Due to mail server malfunction, this patch was sent twice. Please
>> ignore this duplicate.
>
> This submission had another problem too.
>
> Do not use the date of your commit as the date that gets put into
> your email headers.
I don't. This is standard git-send-email 1.7.11.7.
>
> This makes all of your patch submissions look like they occurred in
> the past, and this mixes up the ordering of patches in patchwork.
They did occur in the past. Just like all e-mail you read, they were
sent before you read them.
I ran git-send-email for this on Thu, 31 Mar 2016 18:01:57 -0700. I
observed that the patch didn't seem to make it to the public lists, so I
figured I screwed something up and I sent it again, with the same results.
Then I went on vacation, and came back today to sort everything out. My
MTA had died, so I restarted it, and ... the backlog of messages was
sent and you read it.
>
> So please resubmit this properly with a normal, current, date in your
> email headers.
OK, I will resend the identical patch for the third time...
next prev parent reply other threads:[~2016-04-08 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 1:01 [PATCH] net: thunderx: Fix broken of_node_put() code David Daney
2016-04-08 16:41 ` David Daney
2016-04-08 20:15 ` David Miller
2016-04-08 20:34 ` David Daney [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-08 20:37 David Daney
2016-03-31 21:42 David Daney
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=570815D2.5050608@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rric@kernel.org \
--cc=sgoutham@cavium.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