scsi: target: Documentation: Correct spelling
Correct spelling problems for Documentation/target/ as reported by codespell. Link: https://lore.kernel.org/r/20230127064005.1558-29-rdunlap@infradead.org Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: "Martin K. Petersen" <martin.petersen@oracle.com> Cc: linux-scsi@vger.kernel.org Cc: target-devel@vger.kernel.org Cc: Jonathan Corbet <corbet@lwn.net> Cc: linux-doc@vger.kernel.org Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
This commit is contained in:
parent
7ab734fc75
commit
c57ac5748b
@ -171,7 +171,7 @@ When the opcode is CMD, the entry in the command ring is a struct
|
|||||||
tcmu_cmd_entry. Userspace finds the SCSI CDB (Command Data Block) via
|
tcmu_cmd_entry. Userspace finds the SCSI CDB (Command Data Block) via
|
||||||
tcmu_cmd_entry.req.cdb_off. This is an offset from the start of the
|
tcmu_cmd_entry.req.cdb_off. This is an offset from the start of the
|
||||||
overall shared memory region, not the entry. The data in/out buffers
|
overall shared memory region, not the entry. The data in/out buffers
|
||||||
are accessible via tht req.iov[] array. iov_cnt contains the number of
|
are accessible via the req.iov[] array. iov_cnt contains the number of
|
||||||
entries in iov[] needed to describe either the Data-In or Data-Out
|
entries in iov[] needed to describe either the Data-In or Data-Out
|
||||||
buffers. For bidirectional commands, iov_cnt specifies how many iovec
|
buffers. For bidirectional commands, iov_cnt specifies how many iovec
|
||||||
entries cover the Data-Out area, and iov_bidi_cnt specifies how many
|
entries cover the Data-Out area, and iov_bidi_cnt specifies how many
|
||||||
|
Loading…
Reference in New Issue
Block a user