From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Herve Codina" <herve.codina@bootlin.com>,
"Rob Herring" <robh@kernel.org>,
"Luca Ceresoli" <luca@lucaceresoli.net>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Peter Rosin" <peda@axentia.se>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Jonas Schwöbel" <jonasschwoebel@yahoo.de>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2 RESEND] i2c: muxes: Add GPIO-detected hotplug I2C
Date: Wed, 18 Nov 2026 13:05:51 +0100 [thread overview]
Message-ID: <av2Ummom57XArTHd@shikoro> (raw)
In-Reply-To: <av2RdnZofdcdU_td@shikoro>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
On Wed, Nov 18, 2026 at 12:52:22PM +0100, Wolfram Sang wrote:
>
> > You are very "helpful".
>
> Yes, I am. And I am "honest" and "experienced".
You might try getting Hans de Goede <hansg@kernel.org> in the loop. He
is way more experienced in getting support for broken / strangely
designed HW into the Linux tree. Maybe he has an idea...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-11-18 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 6:00 [PATCH v1 0/2 RESEND] i2c: muxes: Add GPIO-detected hotplug I2C Svyatoslav Ryhel
2025-10-13 6:00 ` [PATCH v1 1/2 RESEND] dt-bindings: i2c: Document GPIO detected hot-plugged I2C bus Svyatoslav Ryhel
2025-10-13 6:00 ` [PATCH v1 2/2 RESEND] i2c: muxes: Add GPIO-detected hotplug I2C Svyatoslav Ryhel
2025-10-15 22:50 ` [PATCH v1 0/2 " Andi Shyti
2025-10-16 7:00 ` Svyatoslav Ryhel
2025-10-16 7:32 ` Wolfram Sang
2025-10-17 10:29 ` Andi Shyti
2025-10-21 13:25 ` Rob Herring
2026-10-17 17:17 ` Svyatoslav Ryhel
2026-11-18 8:13 ` Herve Codina
2026-11-18 8:40 ` Svyatoslav Ryhel
2026-11-18 11:35 ` Wolfram Sang
2026-11-18 11:44 ` Svyatoslav Ryhel
2026-11-18 11:52 ` Wolfram Sang
2026-11-18 12:05 ` Wolfram Sang [this message]
2025-10-16 7:11 ` Herve Codina
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=av2Ummom57XArTHd@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herve.codina@bootlin.com \
--cc=jonasschwoebel@yahoo.de \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@lucaceresoli.net \
--cc=mirq-linux@rere.qmqm.pl \
--cc=peda@axentia.se \
--cc=robh@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