[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240607111726.12678-6-wsa+renesas@sang-engineering.com>
Date: Fri, 7 Jun 2024 13:17:24 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: linux-i2c@...r.kernel.org
Cc: Easwar Hariharan <eahariha@...ux.microsoft.com>,
Andi Shyti <andi.shyti@...nel.org>,
linux-doc@...r.kernel.org,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH 5/5] docs: i2c: summary: rephrase paragraph explaining the figure
Use 'controller/target' and 'adapter/client' pairs consistently.
Signed-off-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
---
Documentation/i2c/summary.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/i2c/summary.rst b/Documentation/i2c/summary.rst
index b10b6aaafcec..1b5bc7ed46aa 100644
--- a/Documentation/i2c/summary.rst
+++ b/Documentation/i2c/summary.rst
@@ -55,9 +55,9 @@ in a directory specific to the feature they provide, for example
``drivers/media/gpio/`` for GPIO expanders and ``drivers/media/i2c/`` for
video-related chips.
-For the example configuration in figure, you will need a driver for your
-I2C adapter, and drivers for your I2C devices (usually one driver for each
-device).
+For the example configuration in the figure above, you will need one adapter
+driver for the I2C controller, and client drivers for your I2C targets. Usually
+one driver for each client.
Outdated terminology
--------------------
--
2.43.0
Powered by blists - more mailing lists