linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: luca.ceresoli@bootlin.com
To: linux-doc@vger.kernel.org, linux-i2c@vger.kernel.org
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Wolfram Sang <wsa@kernel.org>, Peter Rosin <peda@axentia.se>,
	linux-kernel@vger.kernel.org,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH v2 3/3] docs: i2c: i2c-topology: fix typo
Date: Mon, 22 Aug 2022 11:10:50 +0200	[thread overview]
Message-ID: <20220822091050.47099-4-luca.ceresoli@bootlin.com> (raw)
In-Reply-To: <20220822091050.47099-1-luca.ceresoli@bootlin.com>

From: Luca Ceresoli <luca.ceresoli@bootlin.com>

"intension" should have probably been "intention", however "intent" seems
even better.

Reported-by: Bagas Sanjaya <bagasdotme@gmail.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

---

Changed in v2:
- this patch is new in v2
---
 Documentation/i2c/i2c-topology.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/i2c/i2c-topology.rst b/Documentation/i2c/i2c-topology.rst
index 6f2da7f386fd..65ed76bc979f 100644
--- a/Documentation/i2c/i2c-topology.rst
+++ b/Documentation/i2c/i2c-topology.rst
@@ -102,7 +102,7 @@ When using a mux-locked mux, be aware of the following restrictions:
   I.e. the select-transfer-deselect transaction targeting e.g. device
   address 0x42 behind mux-one may be interleaved with a similar
   operation targeting device address 0x42 behind mux-two. The
-  intension with such a topology would in this hypothetical example
+  intent with such a topology would in this hypothetical example
   be that mux-one and mux-two should not be selected simultaneously,
   but mux-locked muxes do not guarantee that in all topologies.
 
-- 
2.34.1


  parent reply	other threads:[~2022-08-22  9:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  9:10 [PATCH v2 0/3] docs: i2c: rework I2C documentation, part II luca.ceresoli
2022-08-22  9:10 ` [PATCH v2 1/3] docs: i2c: i2c-topology: fix incorrect heading luca.ceresoli
2022-08-23  9:19   ` Peter Rosin
2022-08-22  9:10 ` [PATCH v2 2/3] docs: i2c: i2c-topology: reorder sections more logically luca.ceresoli
2022-08-23  9:26   ` Peter Rosin
2022-08-23 21:01     ` Luca Ceresoli
2022-08-24  7:25       ` Peter Rosin
2022-08-22  9:10 ` luca.ceresoli [this message]
2022-08-22 13:40   ` [PATCH v2 3/3] docs: i2c: i2c-topology: fix typo Bagas Sanjaya
2022-08-23  8:33     ` Luca Ceresoli
2022-08-23  9:28   ` Peter Rosin

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=20220822091050.47099-4-luca.ceresoli@bootlin.com \
    --to=luca.ceresoli@bootlin.com \
    --cc=bagasdotme@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=wsa@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 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).