From: Wolfram Sang <wsa@kernel.org>
To: Zev Weiss <zev@bewilderbeest.net>, Peter Rosin <peda@axentia.se>
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-i2c@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ic2: mux: pca9541: add delayed-release support
Date: Mon, 28 Feb 2022 18:19:57 +0100 [thread overview]
Message-ID: <Yh0EPY/DXtBdScB+@shikoro> (raw)
In-Reply-To: <Yh0CUzBzGJc4zyTR@hatter.bewilderbeest.net>
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
> Ack, thanks. In that case, what's the path forward on getting changes to
> this driver merged? I see sign-offs from Wolfram and Peter on the last few
> commits that touched it -- any input from the i2c/i2c-mux maintainers?
For the i2c mux subsystem, I usually wait for Peter's review.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: Zev Weiss <zev@bewilderbeest.net>, Peter Rosin <peda@axentia.se>
Cc: devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-i2c@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v2 0/2] ic2: mux: pca9541: add delayed-release support
Date: Mon, 28 Feb 2022 18:19:57 +0100 [thread overview]
Message-ID: <Yh0EPY/DXtBdScB+@shikoro> (raw)
In-Reply-To: <Yh0CUzBzGJc4zyTR@hatter.bewilderbeest.net>
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
> Ack, thanks. In that case, what's the path forward on getting changes to
> this driver merged? I see sign-offs from Wolfram and Peter on the last few
> commits that touched it -- any input from the i2c/i2c-mux maintainers?
For the i2c mux subsystem, I usually wait for Peter's review.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-28 17:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 0:18 [PATCH v2 0/2] ic2: mux: pca9541: add delayed-release support Zev Weiss
2022-02-01 0:18 ` Zev Weiss
2022-02-01 0:18 ` [PATCH v2 1/2] i2c: " Zev Weiss
2022-02-01 0:18 ` Zev Weiss
2022-02-01 0:18 ` [PATCH v2 2/2] dt-bindings: i2c: add nxp,pca9541 release-delay-us property Zev Weiss
2022-02-01 0:18 ` [PATCH v2 2/2] dt-bindings: i2c: add nxp, pca9541 " Zev Weiss
2022-02-09 21:47 ` [PATCH v2 2/2] dt-bindings: i2c: add nxp,pca9541 " Rob Herring
2022-02-09 21:47 ` Rob Herring
2022-02-28 8:43 ` [PATCH v2 0/2] ic2: mux: pca9541: add delayed-release support Zev Weiss
2022-02-28 8:43 ` Zev Weiss
2022-02-28 13:57 ` Guenter Roeck
2022-02-28 13:57 ` Guenter Roeck
2022-02-28 17:11 ` Zev Weiss
2022-02-28 17:11 ` Zev Weiss
2022-02-28 17:19 ` Wolfram Sang [this message]
2022-02-28 17:19 ` Wolfram Sang
2022-02-28 18:10 ` Guenter Roeck
2022-02-28 18:10 ` Guenter Roeck
2022-02-28 21:54 ` Peter Rosin
2022-02-28 21:54 ` Peter Rosin
2022-02-28 22:38 ` Zev Weiss
2022-02-28 22:38 ` Zev Weiss
2022-03-02 14:43 ` Peter Rosin
2022-03-02 14:43 ` Peter Rosin
2022-03-03 0:43 ` Zev Weiss
2022-03-03 0:43 ` Zev Weiss
2022-03-18 11:00 ` Wolfram Sang
2022-03-18 11:00 ` Wolfram Sang
2022-03-21 22:32 ` Zev Weiss
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=Yh0EPY/DXtBdScB+@shikoro \
--to=wsa@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.org \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=zev@bewilderbeest.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.