From: Peter Rosin <peda@axentia.se>
To: Patrick Rudolph <patrick.rudolph@9elements.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-i2c@vger.kernel.org
Cc: naresh.solanki@9elements.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v15 0/4] Add support for Maxim MAX735x/MAX736x variants
Date: Thu, 17 Aug 2023 18:21:46 +0200 [thread overview]
Message-ID: <b40e0dce-4e7b-8599-734f-d6e70fdfbb7a@axentia.se> (raw)
In-Reply-To: <20230817071056.2125679-1-patrick.rudolph@9elements.com>
Hi!
2023-08-17 at 09:10, Patrick Rudolph wrote:
> v15:
> - Clarified VDD usage on PCA9846 which has two VDD pins
>
> v14:
> - Added comment for interrupt support
>
*snip*
This has gone on for far too long and the series feels more than ready...
Thanks for your persistence!
Cheers,
Peter
prev parent reply other threads:[~2023-08-17 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 7:10 [PATCH v15 0/4] Add support for Maxim MAX735x/MAX736x variants Patrick Rudolph
2023-08-17 7:10 ` [PATCH v15 1/4] dt-bindings: i2c: pca954x: Correct interrupt support Patrick Rudolph
2023-08-17 16:21 ` Peter Rosin
2023-08-23 21:15 ` Wolfram Sang
2023-08-23 21:21 ` Wolfram Sang
2023-08-17 7:10 ` [PATCH v15 2/4] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants Patrick Rudolph
2023-08-17 16:22 ` Peter Rosin
2023-08-23 21:15 ` Wolfram Sang
2023-08-17 7:10 ` [PATCH v15 3/4] i2c: muxes: pca954x: Add MAX735x/MAX736x support Patrick Rudolph
2023-08-17 16:22 ` Peter Rosin
2023-08-20 11:23 ` Andi Shyti
2023-08-21 6:20 ` Patrick Rudolph
2023-08-23 21:15 ` Wolfram Sang
2023-08-17 7:10 ` [PATCH v15 4/4] i2c: muxes: pca954x: Add regulator support Patrick Rudolph
2023-08-17 16:22 ` Peter Rosin
2023-08-23 21:20 ` Wolfram Sang
2023-08-17 16:21 ` Peter Rosin [this message]
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=b40e0dce-4e7b-8599-734f-d6e70fdfbb7a@axentia.se \
--to=peda@axentia.se \
--cc=devicetree@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.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