From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James.Bottomley@HansenPartnership.com, linux-scsi@vger.kernel.org
Subject: [PATCH 0 of 6] SCSI Data Integrity Support
Date: Thu, 17 Jul 2008 04:28:29 -0400 [thread overview]
Message-ID: <patchbomb.1216283309@sermon.lab.mkp.net> (raw)
These patches are against Linus' current git tree which now has all of
the block layer data integrity code + the preparatory SCSI bits.
Changes since last post:
- Fixed a bug in error handling when HBA detected an integrity error.
- Introduced prot_type in scsi_cmnd which informs the HBA of the
target type. This is necessary because the HBA needs to know which
fields in the protection information to check and that depends on
the target type.
--
Martin K. Petersen Oracle Linux Engineering
next reply other threads:[~2008-07-17 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 8:28 Martin K. Petersen [this message]
2008-07-17 8:28 ` [PATCH 1 of 6] scsi: Host protection capabilities Martin K. Petersen
2008-07-17 8:28 ` [PATCH 2 of 6] scsi: Command protection operation Martin K. Petersen
2008-07-17 8:28 ` [PATCH 3 of 6] scsi: Support devices with protection information Martin K. Petersen
2008-07-17 17:53 ` James Bottomley
2008-07-17 18:39 ` Martin K. Petersen
2008-07-17 20:42 ` Michael Hernandez
2008-07-17 21:08 ` Martin K. Petersen
2008-07-17 8:28 ` [PATCH 4 of 6] scsi: Do not retry a request whose data integrity check failed Martin K. Petersen
2008-07-17 8:28 ` [PATCH 5 of 6] sd: Identify DIF protection type and application tag ownership Martin K. Petersen
2008-07-17 8:28 ` [PATCH 6 of 6] sd: Support for SCSI disk (SBC) Data Integrity Field Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2008-07-10 2:48 [PATCH 0 of 6] SCSI Data Integrity Support Martin K. Petersen
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=patchbomb.1216283309@sermon.lab.mkp.net \
--to=martin.petersen@oracle.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.