[PATCH 11/35 v2] Documentation: i2c: correct spelling

* [PATCH 11/35 v2] Documentation: i2c: correct spelling
@ 2023-01-28 19:21 Randy Dunlap
  2023-02-02 21:28 ` Wolfram Sang
  0 siblings, 1 reply; 3+ messages in thread
From: Randy Dunlap @ 2023-01-28 19:21 UTC (permalink / raw)
  To: linux-kernel
  Cc: Randy Dunlap, Wolfram Sang, linux-i2c, Jonathan Corbet, linux-doc

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

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
---
v2: add correction for "an other" -> "another"

 Documentation/i2c/gpio-fault-injection.rst |    2 +-
 Documentation/i2c/smbus-protocol.rst       |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff -- a/Documentation/i2c/gpio-fault-injection.rst b/Documentation/i2c/gpio-fault-injection.rst

--- a/Documentation/i2c/gpio-fault-injection.rst
+++ b/Documentation/i2c/gpio-fault-injection.rst
@@ -93,7 +93,7 @@ bus arbitration against another master i
 ------------------
 
 This file is write only and you need to write the duration of the arbitration
-intereference (in µs, maximum is 100ms). The calling process will then sleep
+interference (in µs, maximum is 100ms). The calling process will then sleep
 and wait for the next bus clock. The process is interruptible, though.
 
 Arbitration lost is achieved by waiting for SCL going down by the master under
diff -- a/Documentation/i2c/smbus-protocol.rst b/Documentation/i2c/smbus-protocol.rst
--- a/Documentation/i2c/smbus-protocol.rst
+++ b/Documentation/i2c/smbus-protocol.rst
@@ -238,7 +238,7 @@ This is implemented in the following way
 * I2C bus drivers trigger SMBus Host Notify by a call to
   i2c_handle_smbus_host_notify().
 * I2C drivers for devices which can trigger SMBus Host Notify will have
-  client->irq assigned to a Host Notify IRQ if noone else specified an other.
+  client->irq assigned to a Host Notify IRQ if no one else specified another.
 
 There is currently no way to retrieve the data parameter from the client.
 

^ permalink raw reply	[flat|nested] 3+ messages in thread