Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Sivakumar.Subramani@neterion.com
Cc: leitao@linux.vnet.ibm.com, netdev@vger.kernel.org,
	Sreenivasa.Honnur@neterion.com, Ramkrishna.Vepa@neterion.com
Subject: Re: [PATCH] s2io: fixing a ethtool test that is broken
Date: Fri, 13 Nov 2009 19:36:00 -0800 (PST)	[thread overview]
Message-ID: <20091113.193600.215645997.davem@davemloft.net> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD7705E74E6F@nekter>

From: "Sivakumar Subramani" <Sivakumar.Subramani@neterion.com>
Date: Thu, 12 Nov 2009 13:59:53 -0500

> [Siva] Reviewed the patch. Please accept it.
> 
> Acked-by: Sivakumar Subramani <sivakumar.subramani@neterion.com>

Please use reasonable mechanisms to reply to patches when you review
them.  Something in your mail client software or elsewhere has messed
with the Message-Id and other elements of the email headers, and
therefore the threading of messages so that patchwork and other tools
can attach your reply to the patch posting itself simply do not work.

This makes more work for me and I am not going to go searching for
your replies by hand.

So you should fix this because otherwise your review reply ACKs
will get lost.

Also you have this very non-standard way to attributing your content
by adding these "[Name]" tags.  Please don't do that, it is
non-standard and therefore most people don't understand it at all.

The normal email reply quoting mechanisms of your email client will
let us know exactly what parts are written by you, and what parts are
said by other people in quoted text.

Thank you.

  reply	other threads:[~2009-11-14  3:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 19:44 [PATCH] s2io: fixing a ethtool test that is broken leitao
2009-11-12 18:59 ` Sivakumar Subramani
2009-11-14  3:36   ` David Miller [this message]
2009-11-14  3:57 ` David Miller

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=20091113.193600.215645997.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Ramkrishna.Vepa@neterion.com \
    --cc=Sivakumar.Subramani@neterion.com \
    --cc=Sreenivasa.Honnur@neterion.com \
    --cc=leitao@linux.vnet.ibm.com \
    --cc=netdev@vger.kernel.org \
    /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