linux-kernel - Re: [PATCH 5/5] docs: i2c: summary: rephrase paragraph explaining the figure

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: <760abc2e-d6d6-41a4-8691-09e4040dd1b4@linux.microsoft.com>
Date: Fri, 7 Jun 2024 11:17:49 -0700
From: Easwar Hariharan <eahariha@...ux.microsoft.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>, linux-i2c@...r.kernel.org
Cc: eahariha@...ux.microsoft.com, Andi Shyti <andi.shyti@...nel.org>,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] docs: i2c: summary: rephrase paragraph explaining the
 figure

On 6/7/2024 4:17 AM, Wolfram Sang wrote:
> 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
>  --------------------

Similar feedback as for patch 4. I thought we agreed on using {local,
remote} target for in-line clarity.

Thanks,
Easwar