From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH v2 1/2] net/mlx4_core: clean up cq_res_start_move_to()
Date: Thu, 16 Jan 2014 11:39:47 -0800 (PST)
Message-ID: <20140116.113947.1353295150580987909.davem@davemloft.net>
References: <20140114084752.1db64b21@jpm-OptiPlex-GX620>
	<1389728736.28068.8.camel@x220>
	<20140116094639.6fe72bcf@jpm-OptiPlex-GX620>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pebolle@tiscali.nl, ogerlitz@mellanox.com, ronye@mellanox.com,
	hadarh@mellanox.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
To: jackm@dev.mellanox.co.il
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20140116094639.6fe72bcf@jpm-OptiPlex-GX620>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

From: Jack Morgenstein <jackm@dev.mellanox.co.il>
Date: Thu, 16 Jan 2014 09:46:39 +0200

> ACK.  OK.

This is not the correct way to ack a patch.

First of all, you should not top post.  Instead you should quote
the relevant parts of the email you are replying to, and then add
your new content underneath.

In this circumstance, the "relevant parts" are just the commit log
message from the patch submitter.  There is no reason ever to quote
the patch itself unless you are making comments on specific parts.

And you specify your ACK using a properly formed "Acked-by: "
line.

Please look at how other reviewers ACK patches.

Thank you.