From: Eric Moore <eric.moore@lsi.com>
To: linux-scsi@vger.kernel.org
Cc: James.Bottomley@HansenPartnership.com
Subject: [PATCH 0/14 - 2nd post] mpt2sas: driver version 01.100.02.00
Date: Fri, 17 Apr 2009 10:24:06 -0600 [thread overview]
Message-ID: <20090417162404.GA7009@lsil.com> (raw)
2nd Post:
Per Martin Petersen suggestions on T10 DIF - For type 1 protection
only set reference and gaurd tag checking. For type 3 protection only
set guard tag checking. Deleted the calling of scsi_host_set_guard.
1st Post:
Here is set of misc bug fix's, to include T10 DIF support, and Lun Reset
Support.
Please consider for inclusion.
Signed-off-by: Eric Moore <eric.moore@lsi.com>
[PATCH 1/14 - 2nd post] mpt2sas: unique ioctl magic number
[PATCH 2/14 - 2nd post] mpt2sas: the sanity check in base_interrupt needs to be on dword boundary
[PATCH 3/14 - 2nd post] mpt2sas: fix oops when firmware sends large sense buffer size
[PATCH 4/14 - 2nd post] mpt2sas: running out of message frames
[PATCH 5/14 - 2nd post] mpt2sas: driver name needs to be in the MPT2IOCINFO ioctl
[PATCH 6/14 - 2nd post] mpt2sas: Identify Dell series-7 adapters at driver load time.
[PATCH 7/14 - 2nd post] mpt2sas: Broadcast Primative AEN bug fix.
[PATCH 8/14 - 2nd post] mpt2sas: release diagnotic buffers prior host reset
[PATCH 9/14 - 2nd post] mpt2sas: T10 DIF Support - EEDP
[PATCH 10/14 - 2nd post] mpt2sas: LUN Reset Support
[PATCH 11/14 - 2nd post] mpt2sas: add query task support for MPT2COMMAND ioctl
[PATCH 12/14 - 2nd post] mpt2sas: using the same naming convention for all static function
[PATCH 13/14 - 2nd post] mpt2sas: fix hotplug event processing
[PATCH 14/14 - 2nd post] mpt2sas: bump driver version to 01.100.02.00
next reply other threads:[~2009-04-17 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 16:24 Eric Moore [this message]
2009-04-21 15:08 ` [PATCH 0/14 - 2nd post] mpt2sas: driver version 01.100.02.00 Moore, Eric
2009-04-21 15:25 ` James Bottomley
2009-04-21 21:03 ` Moore, Eric
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=20090417162404.GA7009@lsil.com \
--to=eric.moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.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.