From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Garzik <jeff@garzik.org>
Subject: Re: [PATCH 1/5] mvsas: bug fix with setting task management frame
 type
Date: Thu, 14 May 2009 00:46:22 -0400
Message-ID: <4A0BA21E.9090508@garzik.org>
References: <20090511171944.GA9698@Andy.marvell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <linux-scsi-owner@vger.kernel.org>
Received: from srv5.dvmed.net ([207.36.208.214]:53576 "EHLO mail.dvmed.net"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751159AbZENEqY (ORCPT <rfc822;linux-scsi@vger.kernel.org>);
	Thu, 14 May 2009 00:46:24 -0400
In-Reply-To: <20090511171944.GA9698@Andy.marvell.com>
Sender: linux-scsi-owner@vger.kernel.org
List-Id: linux-scsi@vger.kernel.org
To: ayan@marvell.com
Cc: linux-scsi@vger.kernel.org, james.bottomley@hansenpartnership.com


Additional request:

When revising a patch, please indicate revision in the email subject 
line or email body.

For example:

1) Initial posting:

     Subject:
	[PATCH 5/5] mvsas: optimization of code

     Body:
	patch description
	patch content

2) First revision, removing void* casts:

     Subject:
	[PATCH 5/5 v2] mvsas: optimization of code

     Body:
	patch description
	---
	"v2: updated to remove void* casts"
	patch content

3) Second revision, making some other example change:

     Subject:
	[PATCH 5/5 v3] mvsas: optimization of code

     Body:
	patch description
	---
	"v3: description of third change..."
	"v2: updated to remove void* casts"
	patch content

James or others may have other suggestions, but this is the basic idea 
for revising patches.

This accomplishes two goals:

	a) Indicate email containing latest changes
	b) Describe changes from previous patch revision

Best regards,

	Jeff