Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
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
Message-Id: <20220822091050.47099-4-luca.ceresoli@bootlin.com>
In-Reply-To: <20220822091050.47099-1-luca.ceresoli@bootlin.com>
References: <20220822091050.47099-1-luca.ceresoli@bootlin.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

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