From: "wsa@kernel.org" <wsa@kernel.org>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"andi.shyti@kernel.org" <andi.shyti@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 1/2] dt-bindings: i2c: add bus-reset-gpios property
Date: Tue, 19 Dec 2023 21:50:25 +0100 [thread overview]
Message-ID: <ZYICEczlao+pg8kd@shikoro> (raw)
In-Reply-To: <601d07b5-264d-4322-b92e-63d58b3d69fa@alliedtelesis.co.nz>
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
> I personally would like to see it accepted but it seems there are
> objections to this approach. I've yet to come up with anything better to
> offer as an alternative.
I see. Thanks for the heads up!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-19 20:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 3:57 [PATCH v6 0/2] i2c: bus-reset-gpios Chris Packham
2023-11-15 3:57 ` [PATCH v6 1/2] dt-bindings: i2c: add bus-reset-gpios property Chris Packham
2023-11-15 21:29 ` Krzysztof Kozlowski
2023-11-15 21:53 ` Chris Packham
2023-11-16 11:37 ` Krzysztof Kozlowski
2023-12-19 17:02 ` wsa
2023-12-19 19:28 ` Chris Packham
2023-12-19 20:50 ` wsa [this message]
2023-12-19 23:25 ` Andi Shyti
2023-12-20 7:22 ` Krzysztof Kozlowski
2023-12-20 11:03 ` wsa
2023-12-20 11:29 ` Krzysztof Kozlowski
2023-12-20 11:52 ` wsa
2023-12-21 0:40 ` Andi Shyti
2023-11-15 3:57 ` [PATCH v6 2/2] i2c: add an optional " Chris Packham
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=ZYICEczlao+pg8kd@shikoro \
--to=wsa@kernel.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).