From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andy Yan <ayan@marvell.com>
Cc: jeff@garzik.org, Tejun Heo <tj@kernel.org>,
linux-scsi@vger.kernel.org, Michael Wang <qswang@marvell.com>,
Jacky Feng <jfeng@marvell.com>, Ying Chu <jasonchu@marvell.com>,
Ke Wei <kewei@marvell.com>
Subject: Re: [PATCH 0/3] mvsas updated for 88SE64xx and 88SE94xx
Date: Fri, 27 Mar 2009 16:53:21 +0000 [thread overview]
Message-ID: <1238172801.3292.20.camel@localhost.localdomain> (raw)
In-Reply-To: <FE3F06125A99254E8D92161AA4569C6F0693DCE5@sc-exch02.marvell.com>
On Thu, 2009-03-19 at 01:49 -0700, Andy Yan wrote:
> Greetings all,
> Here are updated mvsas driver with bugfixes and new features.
> This version contains following main changes
> - Switch to new layout to support more types of ASIC.
> - SSP TMF supported and related Error Handing enhanced.
> - Support flash feature with delay 2*HZ when PHY changed.
> - Support Marvell 94xx series ASIC for 6G SAS/SATA, which has 2
> 88SE64xx chips but any different register description.
> - Support SPI flash for HBA-related configuration info.
> - Other patch enhanced from kernel side such as increasing PHY type
> detection wait time. (http://lkml.org/lkml/2009/1/15/502)
>
> The first patch is to update the Makefile and Kconfig for layout change.
> The second patch is to add the code for common use with ASICs.
> The thirst patch is to add the code for ASIC specific function and const
> value.
> The subjects of all patches are
> [PATCH 1/3] Layout changes for new mvsas
> [PATCH 2/3] Common code for init and runtime
> [PATCH 3/3] ASIC specific
This looks fine.
The patch is still wrapped, though. If you can't fix the mail client,
just do a text/plain attachment ... I can pull that into git.
Thanks,
James
next prev parent reply other threads:[~2009-03-27 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 8:49 [PATCH 0/3] mvsas updated for 88SE64xx and 88SE94xx Andy Yan
2009-03-27 16:53 ` James Bottomley [this message]
2009-04-07 11:48 ` Andy Yan
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=1238172801.3292.20.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=ayan@marvell.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=tj@kernel.org \
/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.