All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Ke Wei <kewei.mv@gmail.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi@vger.kernel.org, qswang@marvell.com,
	jfeng@marvell.com, qzhao@marvell.com, kewei@marvell.com
Subject: Re: [PATCH] Marvell 6440 SAS/SATA driver
Date: Wed, 06 Feb 2008 19:33:13 -0500	[thread overview]
Message-ID: <47AA51C9.4040005@garzik.org> (raw)
In-Reply-To: <20080205131920.GA7901@ubuntu.domain>

Ke Wei wrote:
> Added support for hotplug and wide port.
> 
> 
> Signed-off-by: Ke Wei <kewei@marvell.com>
> ---
>  drivers/scsi/mvsas.c |  445 ++++++++++++++++++++++++++++++++++++++------------
>  1 files changed, 339 insertions(+), 106 deletions(-)

Technically speaking, everything is looking great so far.

We need to correct one process problem, and we should be able to get 
your work into the 'mvsas' branch of scsi-misc-2.6.git... and soon 
thereafter hopefully into the official upstream kernel.

The process problem is...  when making revisions, we need to get the 
full patch each time.  In this case, each patch should be diff'd against 
the current version in the 'mvsas' branch:  version 0.1.

The succession of emails would look like this:

Email #1:

	Subject: [PATCH] mvsas: make it work

	Convert the skeleton mvsas driver into a real, working
	driver.  Currently, the following works:

	SAS, SAS expanders, SAS wide ports
	SATA devices, SATAPI

	Signed-off-by: Ke Wei <kewei@marvell.com>


And then James, myself, other reviewers reply.  Or, you add some new 
features like hotplugging.

Each time, you must regenerate a full patch against the most git 
repository revision:

	If a previous patch of yours, version "0.2", has been applied
	to git, then you would create your patch against version 0.2.

	If a previous patch of yours has NOT yet been applied to git,
	then you would create your patch against version 0.1.

Thus, in this case, version 0.1 is in 'mvsas' branch, so your second 
email would then be

Email #2:

	Subject: [PATCH v2] mvsas: make it work

	Convert the skeleton mvsas driver into a real, working
	driver.  Currently, the following works:

	SAS, SAS expanders, SAS wide ports
	SATA devices, SATAPI

	Signed-off-by: Ke Wei <kewei@marvell.com>
	---
	Changes since last posting (version 0.2):
	- fix coding problem


And then you continue your work, and add another revision while everyone 
else is sleeping, the third email would look like:

Email #3:

	Subject: [PATCH v3] mvsas: make it work

	Convert the skeleton mvsas driver into a real, working
	driver.  Currently, the following works:

	SAS, SAS expanders, SAS wide ports
	SATA devices, SATAPI

	Signed-off-by: Ke Wei <kewei@marvell.com>
	---
	Changes since last posting (version 0.3):
	- add hotplug support
	- add wide port support

	Changes since last posting (version 0.2):
	- fix coding problem


Thus, you always create a patch against the most recent source code in 
the git repository.

It is common for patches to go through a few revisions on the mailing 
list, before it is applied to the git repository.

So anyway...  send a patch against the latest #mvsas (version 0.1), and 
that patch should go in rapidly.

Thanks!  And keep up the good work,

	Jeff




  parent reply	other threads:[~2008-02-07  0:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080122151857.GA8680@ubuntu.domain>
2008-01-22 15:24 ` [PATCH] Marvell 6440 SAS/SATA driver Ke Wei
2008-01-23  3:58   ` Jeff Garzik
2008-01-23 10:54     ` Ke Wei
2008-01-23 11:41       ` Jeff Garzik
2008-01-25 16:43         ` Ke Wei
2008-01-25 17:24           ` Grant Grundler
2008-01-25 17:38             ` James Bottomley
2008-01-25 22:12             ` Jeff Garzik
2008-01-25 17:38           ` Grant Grundler
2008-01-25 22:39           ` James Bottomley
2008-01-27 15:10             ` Ke Wei
2008-01-27 15:27             ` Ke Wei
2008-01-27 18:13               ` James Bottomley
2008-02-05 13:19                 ` Ke Wei
2008-02-05 21:00                   ` Luben Tuikov
2008-02-07  0:33                   ` Jeff Garzik [this message]
2008-01-25 23:00           ` James Bottomley
2008-01-25 23:05             ` Jeff Garzik
2008-01-25 21:27       ` James Bottomley
2008-01-23 19:23     ` Grant Grundler
     [not found] <FE3F06125A99254E8D92161AA4569C6F02310B1A@sc-exch02.marvell.com>
2008-02-22 16:26 ` Jeff Garzik
2008-02-22 16:38   ` James Bottomley

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=47AA51C9.4040005@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jfeng@marvell.com \
    --cc=kewei.mv@gmail.com \
    --cc=kewei@marvell.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=qswang@marvell.com \
    --cc=qzhao@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.