From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>
Cc: Peter Rosin <peda@axentia.se>, Andi Shyti <andi.shyti@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Peter Korsgaard <peter.korsgaard@barco.com>,
Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>,
Christopher Cordahi <christophercordahi@nanometrics.ca>
Subject: Re: [PATCH v3 1/3] dt-bindings: i2c: gpio: Add 'settle-time-us' property
Date: Fri, 12 Jul 2024 09:00:23 +0200 [thread overview]
Message-ID: <ZpDUhxjIxzxfabFG@shikoro> (raw)
In-Reply-To: <20240617120818.81237-2-bastien.curutchet@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 124 bytes --]
$subject should be "mux-gpio" instead of just "gpio". It could be mixed
up with the i2c-gpio controller driver otherwise.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-07-12 7:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 12:08 [PATCH v3 0/3] i2c: mux: gpio: Add 'settle-time-us' property Bastien Curutchet
2024-06-17 12:08 ` [PATCH v3 1/3] dt-bindings: i2c: " Bastien Curutchet
2024-06-17 12:19 ` Krzysztof Kozlowski
2024-07-09 21:42 ` Andi Shyti
2024-07-10 8:01 ` Peter Rosin
2024-07-12 7:00 ` Wolfram Sang [this message]
2024-06-17 12:08 ` [PATCH v3 2/3] i2c: mux: gpio: Re-order #include to match alphabetic order Bastien Curutchet
2024-07-09 21:42 ` Andi Shyti
2024-07-10 8:02 ` Peter Rosin
2024-06-17 12:08 ` [PATCH v3 3/3] i2c: mux: gpio: Add support for the 'settle-time-us' property Bastien Curutchet
2024-07-09 21:43 ` Andi Shyti
2024-07-10 8:02 ` Peter Rosin
2024-07-12 6:58 ` Wolfram Sang
2024-07-03 9:35 ` [PATCH v3 0/3] i2c: mux: gpio: Add " Bastien Curutchet
2024-07-09 21:45 ` Andi Shyti
2024-07-10 8:04 ` Peter Rosin
2024-07-16 18:28 ` Andi Shyti
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=ZpDUhxjIxzxfabFG@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=christophercordahi@nanometrics.ca \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=peter.korsgaard@barco.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wsa@kernel.org \
/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