From: Andi Shyti <andi.shyti@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: i2c: mux: i2c-demux-pinctrl: Drop i2c-mux.yaml reference
Date: Wed, 6 Mar 2024 12:51:40 +0100 [thread overview]
Message-ID: <u54h4yntxdolfhyqfhxs3h7htlih3zzndt343ktznlcbrevya2@aeumthqcyuki> (raw)
In-Reply-To: <e6cuggewnewxp2tf4g45jkazu46pgiffooo6gdwi2ge44itsps@njsz64u5vjyr>
Hi Rob,
On Wed, Mar 06, 2024 at 08:20:27AM +0100, Andi Shyti wrote:
> On Tue, Mar 05, 2024 at 12:06:05PM -0600, Rob Herring wrote:
> > On Mon, Feb 26, 2024 at 4:48 AM Wolfram Sang
> > > On Sat, Feb 03, 2024 at 09:50:13PM +0100, Wolfram Sang wrote:
> > > > On Wed, Jan 24, 2024 at 01:05:50PM -0600, Rob Herring wrote:
> > > > > The I2C de-mux is different than an I2C mux, so i2c-mux.yaml is not
> > > > > relevant and shouldn't be referenced.
> > > > >
> > > > > Signed-off-by: Rob Herring <robh@kernel.org>
> > > >
> > > > Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > >
> > > Andi, can you pick these up?
> >
> > I already did since you gave your reviewed-by and they hadn't
> > otherwise been picked up.
>
> Oh... I had them in my test branch and was waiting for some more
> tests before sending the notification.
>
> Shall I remove them from my list?
Because I need to update my branches, I am going to take these
two patches out. Please, let me know if you want me to take them
back in.
Thanks,
Andi
prev parent reply other threads:[~2024-03-06 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 19:05 [PATCH 1/2] dt-bindings: i2c: mux: i2c-demux-pinctrl: Drop i2c-mux.yaml reference Rob Herring
2024-01-24 19:05 ` [PATCH 2/2] dt-bindings: i2c: mux: i2c-demux-pinctrl: Define "i2c-parent" constraints Rob Herring
2024-02-03 20:50 ` Wolfram Sang
2024-02-03 20:50 ` [PATCH 1/2] dt-bindings: i2c: mux: i2c-demux-pinctrl: Drop i2c-mux.yaml reference Wolfram Sang
2024-02-26 10:41 ` Wolfram Sang
2024-03-05 18:06 ` Rob Herring
2024-03-06 7:20 ` Andi Shyti
2024-03-06 11:51 ` Andi Shyti [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=u54h4yntxdolfhyqfhxs3h7htlih3zzndt343ktznlcbrevya2@aeumthqcyuki \
--to=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).