linux-kernel - [PATCH v3 1/3] docs: i2c: i2c-topology: fix typo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20220824083104.2267000-2-luca.ceresoli@bootlin.com>
Date:   Wed, 24 Aug 2022 10:31:02 +0200
From:   luca.ceresoli@...tlin.com
To:     linux-doc@...r.kernel.org, linux-i2c@...r.kernel.org
Cc:     Luca Ceresoli <luca.ceresoli@...tlin.com>,
        Wolfram Sang <wsa@...nel.org>, Peter Rosin <peda@...ntia.se>,
        linux-kernel@...r.kernel.org,
        Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
        Bagas Sanjaya <bagasdotme@...il.com>
Subject: [PATCH v3 1/3] docs: i2c: i2c-topology: fix typo

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

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

Reported-by: Bagas Sanjaya <bagasdotme@...il.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@...tlin.com>
Acked-by: Peter Rosin <peda@...ntia.se>

---

Changed in v3:
- moved as first patch (Bagas)

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 7cb53819778e..c9ed3b4d6085 100644
--- a/Documentation/i2c/i2c-topology.rst
+++ b/Documentation/i2c/i2c-topology.rst
@@ -103,7 +103,7 @@ ML2. It is not safe to build arbitrary topologies with two (or more)
      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