linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org
Subject: [PATCH 7/9] Documentation: scsi: correct spelling
Date: Sun, 29 Jan 2023 15:10:51 -0800	[thread overview]
Message-ID: <20230129231053.20863-8-rdunlap@infradead.org> (raw)
In-Reply-To: <20230129231053.20863-1-rdunlap@infradead.org>

Correct spelling problems for Documentation/scsi/ as reported
by codespell.

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
---
 Documentation/scsi/ncr53c8xx.rst   |    4 ++--
 Documentation/scsi/sym53c8xx_2.rst |    2 +-
 Documentation/scsi/tcm_qla2xxx.rst |    2 +-
 Documentation/scsi/ufs.rst         |    2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff -- a/Documentation/scsi/ncr53c8xx.rst b/Documentation/scsi/ncr53c8xx.rst
--- a/Documentation/scsi/ncr53c8xx.rst
+++ b/Documentation/scsi/ncr53c8xx.rst
@@ -906,7 +906,7 @@ burst:#x   burst enabled (1<<#x burst tr
         led:0      disable LED support
         =====      ===================
 
-  Donnot enable LED support if your scsi board does not use SDMS BIOS.
+  Do not enable LED support if your scsi board does not use SDMS BIOS.
   (See 'Configuration parameters')
 
 10.2.13 Max wide
@@ -1222,7 +1222,7 @@ Unfortunately, the following common SCSI
 - Bad quality terminators.
 
 On the other hand, either bad cabling, broken devices, not conformant
-devices, ... may cause a SCSI signal to be wrong when te driver reads it.
+devices, ... may cause a SCSI signal to be wrong when the driver reads it.
 
 10.7 IMMEDIATE ARBITRATION boot option
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
diff -- a/Documentation/scsi/sym53c8xx_2.rst b/Documentation/scsi/sym53c8xx_2.rst
--- a/Documentation/scsi/sym53c8xx_2.rst
+++ b/Documentation/scsi/sym53c8xx_2.rst
@@ -703,7 +703,7 @@ Unfortunately, the following common SCSI
 - Bad quality terminators.
 
 On the other hand, either bad cabling, broken devices, not conformant
-devices, ... may cause a SCSI signal to be wrong when te driver reads it.
+devices, ... may cause a SCSI signal to be wrong when the driver reads it.
 
 15. SCSI problem troubleshooting
 ================================
diff -- a/Documentation/scsi/tcm_qla2xxx.rst b/Documentation/scsi/tcm_qla2xxx.rst
--- a/Documentation/scsi/tcm_qla2xxx.rst
+++ b/Documentation/scsi/tcm_qla2xxx.rst
@@ -6,7 +6,7 @@ tcm_qla2xxx Driver Notes
 
 tcm_qla2xxx jam_host attribute
 ------------------------------
-There is now a new module endpoint atribute called jam_host
+There is now a new module endpoint attribute called jam_host
 attribute::
 
 	jam_host: boolean=0/1
diff -- a/Documentation/scsi/ufs.rst b/Documentation/scsi/ufs.rst
--- a/Documentation/scsi/ufs.rst
+++ b/Documentation/scsi/ufs.rst
@@ -206,5 +206,5 @@ Device-Specific Data property named "ref
 is interpreted as frequency in Hz and must match one of the values given in
 the UFS specification. UFS subsystem will attempt to read the value when
 executing common controller initialization. If the value is available, UFS
-subsytem will ensure the bRefClkFreq attribute of the UFS storage device is
+subsystem will ensure the bRefClkFreq attribute of the UFS storage device is
 set accordingly and will modify it if there is a mismatch.

  parent reply	other threads:[~2023-01-29 23:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
2023-01-29 23:10 ` [PATCH 1/9] Documentation: admin-guide: correct spelling Randy Dunlap
2023-01-30  9:35   ` Mukesh Ojha
2023-01-29 23:10 ` [PATCH 2/9] Documentation: driver-api: " Randy Dunlap
2023-01-30 19:11   ` Dan Williams
2023-01-30 19:45   ` Song Liu
2023-01-31  9:10   ` Greg Kroah-Hartman
2023-01-29 23:10 ` [PATCH 3/9] Documentation: hwmon: " Randy Dunlap
2023-01-30  0:39   ` Guenter Roeck
2023-01-29 23:10 ` [PATCH 4/9] Documentation: networking: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 5/9] Documentation: RCU: " Randy Dunlap
2023-01-30  5:24   ` Paul E. McKenney
2023-01-29 23:10 ` [PATCH 6/9] Documentation: scsi/ChangeLog*: " Randy Dunlap
2023-01-29 23:10 ` Randy Dunlap [this message]
2023-01-29 23:10 ` [PATCH 8/9] Documentation: sparc: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 9/9] Documentation: userspace-api: " Randy Dunlap
2023-01-31 12:10 ` [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) patchwork-bot+netdevbpf
2023-01-31 12:17   ` Paolo Abeni
2023-02-02 18:09 ` Jonathan Corbet
2023-02-02 18:33   ` Randy Dunlap
2023-02-02 18:39     ` [dm-devel] " Bart Van Assche
2023-02-02 18:46       ` Jonathan Corbet
2023-02-02 18:54         ` James Bottomley
2023-02-14 16:57 ` (subset) " 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=20230129231053.20863-8-rdunlap@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=jejb@linux.ibm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).