| 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
| ||
|
Message-ID: <20240610081023.8118-7-wsa+renesas@sang-engineering.com> Date: Mon, 10 Jun 2024 10:10:21 +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 v2 6/6] 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 203f6c9b2472..da76c787a6c5 100644 --- a/Documentation/i2c/summary.rst +++ b/Documentation/i2c/summary.rst @@ -60,9 +60,9 @@ Client drivers are kept 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