mirror of https://lore.kernel.org/lkml/
 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,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH v3 1/3] docs: i2c: i2c-topology: fix typo
Date: Wed, 24 Aug 2022 10:31:02 +0200	[thread overview]
Message-ID: <20220824083104.2267000-2-luca.ceresoli@bootlin.com> (raw)
In-Reply-To: <20220824083104.2267000-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>
Acked-by: Peter Rosin <peda@axentia.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


  reply	other threads:[~2022-08-24  8:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  8:31 [PATCH v3 0/3] docs: i2c: rework I2C documentation, part II luca.ceresoli
2022-08-24  8:31 ` luca.ceresoli [this message]
2022-08-25  7:42   ` [PATCH v3 1/3] docs: i2c: i2c-topology: fix typo Wolfram Sang
2022-08-24  8:31 ` [PATCH v3 2/3] docs: i2c: i2c-topology: fix incorrect heading luca.ceresoli
2022-08-25  7:42   ` Wolfram Sang
2022-08-24  8:31 ` [PATCH v3 3/3] docs: i2c: i2c-topology: reorder sections more logically luca.ceresoli
2022-08-25  7:42   ` Wolfram Sang

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=20220824083104.2267000-2-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=thomas.petazzoni@bootlin.com \
    --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

all inboxes | Powered by JetHome®