public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Zong-You Xie <ben717@andestech.com>
To: Andi Shyti <andi.shyti@kernel.org>, 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>, <linux-i2c@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 0/4] i2c: add support for Andes platform
Date: Fri, 24 Apr 2026 10:36:58 +0800	[thread overview]
Message-ID: <aerXSoA5JZKr7d6n@swlinux02> (raw)
In-Reply-To: <20260330-atciic100-v4-0-d40822f63e4e@andestech.com>

Hi all,

Gentle ping on this series — it's been ~4 weeks with no review on the
I2C side. Patch 1 (binding) has Conor's ack; patch 2 (driver) has not
received any feedback yet.

If there's something specific in the driver I should address, I'm happy
to spin a v5. Otherwise, would appreciate a look when you have a moment.

Thanks,
Ben

      parent reply	other threads:[~2026-04-24  3:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30  7:30 [PATCH v4 0/4] i2c: add support for Andes platform Ben Zong-You Xie via B4 Relay
2026-03-30  7:30 ` [PATCH v4 1/4] dt-bindings: i2c: add support for AE350 I2C controller Ben Zong-You Xie via B4 Relay
2026-03-30  7:30 ` [PATCH v4 2/4] i2c: add Andes I2C driver support Ben Zong-You Xie via B4 Relay
2026-03-30  7:30 ` [PATCH v4 3/4] MAINTAINERS: add an entry for Andes I2C driver Ben Zong-You Xie via B4 Relay
2026-03-30  7:30 ` [PATCH v4 4/4] riscv: dts: andes: qilai: add I2C controller Ben Zong-You Xie via B4 Relay
2026-04-24  2:36 ` Ben Zong-You Xie [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=aerXSoA5JZKr7d6n@swlinux02 \
    --to=ben717@andestech.com \
    --cc=alex@ghiti.fr \
    --cc=andi.shyti@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.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 \
    /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