From: Andi Shyti <andi.shyti@kernel.org>
To: Yixun Lan <dlan@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dts: riscv: spacemit: k3: Add i2c nodes
Date: Thu, 26 Mar 2026 23:24:45 +0100 [thread overview]
Message-ID: <acWx_31uT2ffcaSN@zenone.zhora.eu> (raw)
In-Reply-To: <acWxJNK_vZca_xCZ@zenone.zhora.eu>
Hi agagin,
On Thu, Mar 26, 2026 at 11:22:31PM +0100, Andi Shyti wrote:
> On Wed, Mar 25, 2026 at 09:49:25AM +0000, Yixun Lan wrote:
> > Populate all I2C devicetree nodes for SpacemiT K3 SoC.
> >
> > Signed-off-by: Yixun Lan <dlan@kernel.org>
>
> this second patch does not apply on my i2c branch. I'm missing
> some other patches on k3.
>
> Can you please rebase it on top of my i2c/i2c-host branch,
> otherwise I will need to wait for the merge window to open in
> order to take this.
sorry, this has to go through some other path, I'm going to take
patch 1.
Andi
next prev parent reply other threads:[~2026-03-26 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 9:49 [PATCH 0/2] riscv: spacemit: k3: Add I2C support Yixun Lan
2026-03-25 9:49 ` [PATCH 1/2] dt-bindings: i2c: spacemit: k3: Add compatible Yixun Lan
2026-03-25 10:42 ` Troy Mitchell
2026-03-25 13:20 ` Javier Martinez Canillas
2026-03-25 18:16 ` Conor Dooley
2026-03-26 7:47 ` Javier Martinez Canillas
2026-03-25 18:16 ` Conor Dooley
2026-03-26 22:28 ` Andi Shyti
2026-03-25 9:49 ` [PATCH 2/2] dts: riscv: spacemit: k3: Add i2c nodes Yixun Lan
2026-03-25 10:41 ` Troy Mitchell
2026-03-26 22:23 ` Andi Shyti
2026-03-27 2:39 ` Yixun Lan
2026-03-26 22:22 ` Andi Shyti
2026-03-26 22:24 ` Andi Shyti [this message]
2026-03-27 2:05 ` Yixun Lan
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=acWx_31uT2ffcaSN@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.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