linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-i2c@vger.kernel.org
Cc: eahariha@linux.microsoft.com, Andi Shyti <andi.shyti@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] docs: i2c: summary: rephrase paragraph explaining the figure
Date: Fri, 7 Jun 2024 11:17:49 -0700	[thread overview]
Message-ID: <760abc2e-d6d6-41a4-8691-09e4040dd1b4@linux.microsoft.com> (raw)
In-Reply-To: <20240607111726.12678-6-wsa+renesas@sang-engineering.com>

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@sang-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

      reply	other threads:[~2024-06-07 18:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 11:17 [PATCH 0/5] docs: i2c: summary: update and use inclusive wording Wolfram Sang
2024-06-07 11:17 ` [PATCH 1/5] docs: i2c: summary: start sentences consistently Wolfram Sang
2024-06-07 18:13   ` Easwar Hariharan
2024-06-07 11:17 ` [PATCH 2/5] docs: i2c: summary: update I2C specification link Wolfram Sang
2024-06-07 18:14   ` Easwar Hariharan
2024-06-07 11:17 ` [PATCH 3/5] docs: i2c: summary: update speed mode description Wolfram Sang
2024-06-07 18:15   ` Easwar Hariharan
2024-06-07 11:17 ` [PATCH 4/5] docs: i2c: summary: document use of inclusive language Wolfram Sang
2024-06-07 18:13   ` Easwar Hariharan
2024-06-07 21:20     ` Wolfram Sang
2024-06-07 11:17 ` [PATCH 5/5] docs: i2c: summary: rephrase paragraph explaining the figure Wolfram Sang
2024-06-07 18:17   ` Easwar Hariharan [this message]

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=760abc2e-d6d6-41a4-8691-09e4040dd1b4@linux.microsoft.com \
    --to=eahariha@linux.microsoft.com \
    --cc=andi.shyti@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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;
as well as URLs for NNTP newsgroup(s).