From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org
Cc: eahariha@linux.microsoft.com, Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v4 5/6] docs: i2c: summary: document 'local' and 'remote' targets
Date: Fri, 21 Jun 2024 09:10:16 -0700 [thread overview]
Message-ID: <461d332e-966d-4906-b33c-8ea3391c9dea@linux.microsoft.com> (raw)
In-Reply-To: <20240621073015.5443-6-wsa+renesas@sang-engineering.com>
On 6/21/2024 12:30 AM, Wolfram Sang wrote:
> Because Linux can be a target as well, add terminology to differentiate
> between Linux being the target and Linux accessing targets.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> Documentation/i2c/summary.rst | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
Looks good to me.
Reviewed-by: Easwar Hariharan <eahariha@linux.microsoft.com>
next prev parent reply other threads:[~2024-06-21 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 7:30 [PATCH v4 0/6] docs: i2c: summary: update and use inclusive wording Wolfram Sang
2024-06-21 7:30 ` [PATCH v4 1/6] docs: i2c: summary: start sentences consistently Wolfram Sang
2024-06-21 7:30 ` [PATCH v4 2/6] docs: i2c: summary: update I2C specification link Wolfram Sang
2024-06-21 7:30 ` [PATCH v4 3/6] docs: i2c: summary: update speed mode description Wolfram Sang
2024-06-21 7:30 ` [PATCH v4 4/6] docs: i2c: summary: document use of inclusive language Wolfram Sang
2024-06-21 16:09 ` Easwar Hariharan
2024-06-21 7:30 ` [PATCH v4 5/6] docs: i2c: summary: document 'local' and 'remote' targets Wolfram Sang
2024-06-21 16:10 ` Easwar Hariharan [this message]
2024-06-21 7:30 ` [PATCH v4 6/6] docs: i2c: summary: be clearer with 'controller/target' and 'adapter/client' pairs Wolfram Sang
2024-06-21 16:11 ` Easwar Hariharan
2024-06-22 8:14 ` [PATCH v4 0/6] docs: i2c: summary: update and use inclusive wording 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=461d332e-966d-4906-b33c-8ea3391c9dea@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=andi.shyti@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