public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: kewei@marvell.com
Cc: linux-scsi@vger.kernel.org, jeff@garzik.org, qzhao@marvell.com,
	qswang@marvell.com, jfeng@marvell.com,
	Jason Chu <jasonchu@marvell.com>
Subject: Re: [PATCH 1/5] mvsas : redesign the mvsas driver architecture.
Date: Tue, 24 Feb 2009 17:15:18 +0000	[thread overview]
Message-ID: <1235495718.3204.37.camel@localhost.localdomain> (raw)
In-Reply-To: <49A3C100.8040005@marvell.com>

On Tue, 2009-02-24 at 17:42 +0800, Ke Wei wrote:
> We redesign the mvsas driver architecture. Then the driver can support
> Marvell's
> 64 bit PCIE-X SAS/SATA 3Gb/s mv64xx chip and 6Gb/s mv94xx chip based
> host
> adapters. I created a directory for the driver in scsi folder and
> delete the
> original simple driver.
> 
> modify Kconfig entry for the mvsas driver, and change the driver path.
> 
> Signed-off-by: Ke Wei <kewei@marvell.com>
> ---
>  drivers/scsi/Kconfig  |   10 +-
>  drivers/scsi/Makefile |    2 +-
>  drivers/scsi/mvsas.c  | 3222
> -------------------------------------------------
>  3 files changed, 2 insertions(+), 3232 deletions(-)
> 
> diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
> index 256c7be..b64882b 100644
> --- a/drivers/scsi/Kconfig
> +++ b/drivers/scsi/Kconfig
> @@ -1029,15 +1029,7 @@ config SCSI_IZIP_SLOW_CTR
> 
>           Generally, saying N is fine.
> 
> -config SCSI_MVSAS
> -       tristate "Marvell 88SE6440 SAS/SATA support"
> -       depends on PCI && SCSI
> -       select SCSI_SAS_LIBSAS
> -       help
> -         This driver supports Marvell SAS/SATA PCI devices.
> -
> -         To compiler this driver as a module, choose M here: the
> module
> -         will be called mvsas.
> +source "drivers/scsi/mvsas/Kconfig"
> 
>  config SCSI_NCR53C406A
>         tristate "NCR53c406a SCSI support"
> diff --git a/drivers/scsi/Makefile b/drivers/scsi/Makefile
> index 7461eb0..f5bbd99 100644
> --- a/drivers/scsi/Makefile
> +++ b/drivers/scsi/Makefile
> @@ -123,7 +123,7 @@ obj-$(CONFIG_SCSI_IBMVSCSIS)        += ibmvscsi/
>  obj-$(CONFIG_SCSI_IBMVFC)      += ibmvscsi/
>  obj-$(CONFIG_SCSI_HPTIOP)      += hptiop.o
>  obj-$(CONFIG_SCSI_STEX)                += stex.o
> -obj-$(CONFIG_SCSI_MVSAS)       += mvsas.o
> +obj-$(CONFIG_SCSI_MVSAS)       += mvsas/
>  obj-$(CONFIG_PS3_ROM)          += ps3rom.o
>  obj-$(CONFIG_SCSI_CXGB3_ISCSI) += libiscsi.o libiscsi_tcp.o cxgb3i/

Um, this isn't at all the way to split things up because it isn't
bisectable.  This patch removes the driver entirely But adds a
non-existent build directory, so we're left with one bisection point
where the driver is gone.  Your second patch adds back a Kconfig and
Makefile to the directory only, so we're left with a second point where
the build would break because you've added a Makefile but no actual
source files.

What I'd like to see in future is one patch transforming the driver to
the new layout (preferably with no functional changes) and then a series
on top of that adding the new functionality.

I can apply this by combining all five patches into a single one,
restoring bisectability, but if that's the only option and you can't do
a transformation followed by additions, could we at least see a list of
all the new stuff you've added?

Thanks,

James



  reply	other threads:[~2009-02-24 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24  9:42 [PATCH 1/5] mvsas : redesign the mvsas driver architecture Ke Wei
2009-02-24 17:15 ` James Bottomley [this message]
     [not found]   ` <37BE93F844A044459933732A80255042065E0A3A@sc-exch03.marvell.com>
     [not found]     ` <77B579C76B3DE742A499A2EF95859C1FFA61A0@sc-exch03.marvell.com>
2009-03-11 20:54       ` [Linux kernel LibSAS - Task Collector Mode]RE: " James Bottomley
2009-03-12 15:42         ` [Linux kernel LibSAS - Task Collector Mode]RE: [PATCH 1/5]mvsas " Michael Wang

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=1235495718.3204.37.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=jasonchu@marvell.com \
    --cc=jeff@garzik.org \
    --cc=jfeng@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox