From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org
Cc: Stefan Roese <sr@denx.de>, Andi Shyti <andi.shyti@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 37/64] i2c: mt7621: reword according to newest specification
Date: Mon, 25 Mar 2024 09:06:21 +0100 [thread overview]
Message-ID: <97b5904b-af1f-48a4-98b4-13d0531beece@collabora.com> (raw)
In-Reply-To: <20240322132619.6389-38-wsa+renesas@sang-engineering.com>
Il 22/03/24 14:25, Wolfram Sang ha scritto:
> Match the wording of this driver wrt. the newest I2C v7, SMBus 3.2, I3C
> specifications and replace "master/slave" with more appropriate terms.
> They are also more specific because we distinguish now between a remote
> entity ("client") and a local one ("target").
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2024-03-25 8:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 13:24 [PATCH 00/64] i2c: reword i2c_algorithm according to newest specification Wolfram Sang
2024-03-22 13:25 ` [PATCH 37/64] i2c: mt7621: reword " Wolfram Sang
2024-03-25 8:06 ` AngeloGioacchino Del Regno [this message]
2024-03-25 8:07 ` Stefan Roese
2024-03-22 13:25 ` [PATCH 64/64] i2c: reword i2c_algorithm in drivers " Wolfram Sang
2024-03-22 14:34 ` Bjorn Andersson
2024-03-22 15:11 ` Nicolas Ferre
2024-03-22 16:47 ` Wolfram Sang
2024-03-22 17:05 ` Guenter Roeck
2024-03-22 17:09 ` Wolfram Sang
2024-03-22 16:09 ` Andy Shevchenko
2024-03-22 16:48 ` Wolfram Sang
2024-03-22 17:00 ` Andy Shevchenko
2024-03-25 7:45 ` Oleksij Rempel
2024-03-25 7:53 ` Jarkko Nikula
2024-04-02 12:35 ` Linus Walleij
2024-03-23 9:20 ` [PATCH 00/64] i2c: reword i2c_algorithm " Andi Shyti
2024-03-26 0:36 ` Andi Shyti
2024-04-05 8:48 ` 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=97b5904b-af1f-48a4-98b4-13d0531beece@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=andi.shyti@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=sr@denx.de \
--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