From: Jeff Garzik <jeff@garzik.org>
To: Ke Wei <kewei.mv@gmail.com>
Cc: linux-scsi@vger.kernel.org, kewei@marvell.com,
qswang@marvell.com, jfeng@marvell.com,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] Marvell 6440 SAS/SATA driver (draft)
Date: Thu, 10 Jan 2008 02:09:00 -0500 [thread overview]
Message-ID: <4785C48C.50705@garzik.org> (raw)
In-Reply-To: <6b2481670801092253v666e969doe5ec2bd77e10a87e@mail.gmail.com>
Ke Wei wrote:
> The 88SE6440 driver :
>
> The driver is based on bare code from Jeff Garzik. And it can work
> under linux kernel 2.6.23.
> By far, Can discover and find SAS HDD, but SATA is currently
> unsupported. Command queue depth can be above 1.
> Most error handling, and some phy handling code is notably missing.
>
>
> contains the following updates:
>
> --- mvsas_orig.c 2007-12-06 19:21:32.000000000 -0500
> +++ mvsas.c 2008-01-09 04:53:14.000000000 -0500
Fantastic! I'm delighted to see this is moving, and thanks much for
getting the driver to that critical "it works" milestone.
We should note for the linux-scsi audience and potential testers that
the base driver upon which this is based is available on the "sas" branch of
git://git.kernel.org:/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
I will give some substantive comments tomorrow (just got back from long
trip). Two quick suggestions:
1) To make it easier for people to review and test the driver, I would
suggest posting a diff against 2.6.24-rc7 (or 2.6.23), ignoring my
original code. Thus, it would result in a patch
2) In future patches, include a Signed-off-by: line when you are ready
for your patch to be included in the kernel.
Thanks!
Jeff
next prev parent reply other threads:[~2008-01-10 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 6:53 [PATCH] Marvell 6440 SAS/SATA driver (draft) Ke Wei
2008-01-10 7:09 ` Jeff Garzik [this message]
2008-01-10 7:21 ` Jeff Garzik
2008-01-18 17:58 ` James Bottomley
2008-01-18 18:53 ` James Bottomley
2008-01-21 2:43 ` Ke Wei
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=4785C48C.50705@garzik.org \
--to=jeff@garzik.org \
--cc=jfeng@marvell.com \
--cc=kewei.mv@gmail.com \
--cc=kewei@marvell.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=qswang@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.