From: Andi Shyti <andi.shyti@kernel.org>
To: Encrow Thorne <jyc0019@gmail.com>
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, conor+dt@kernel.org,
devicetree@vger.kernel.org, dlan@gentoo.org,
guodong@riscstar.com, krzk+dt@kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, p.zabel@pengutronix.de,
palmer@dabbelt.com, pjw@kernel.org, robh@kernel.org,
spacemit@lists.linux.dev, troy.mitchell@linux.spacemit.com,
troymitchell988@gmail.com
Subject: Re: [PATCH 3/3] riscv: dts: spacemit: add reset property
Date: Wed, 7 Jan 2026 15:22:42 +0100 [thread overview]
Message-ID: <aV5r8k4VKnXX_9Sw@zenone.zhora.eu> (raw)
In-Reply-To: <20251230150653.42097-3-jyc0019@gmail.com>
Hi Encrow,
On Tue, Dec 30, 2025 at 11:06:53PM +0800, Encrow Thorne wrote:
> Add resets property to K1 I2C node.
> ---
> arch/riscv/boot/dts/spacemit/k1.dtsi | 8 ++++++++
> 1 file changed, 8 insertions(+)
how is this patch formatted?
Andi
next prev parent reply other threads:[~2026-01-07 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 14:29 [PATCH v3 0/3] i2c: spacemit: add reset support Encrow Thorne
2025-12-30 15:06 ` [PATCH 1/3] dt-bindings: i2c: spacemit: add optional resets Encrow Thorne
2025-12-30 15:06 ` [PATCH 2/3] i2c: k1: add reset support Encrow Thorne
2025-12-30 15:06 ` [PATCH 3/3] riscv: dts: spacemit: add reset property Encrow Thorne
2026-01-07 14:22 ` Andi Shyti [this message]
2026-01-07 16:23 ` Encrow Thorne
2026-01-07 17:51 ` Andi Shyti
2026-01-05 18:44 ` [PATCH 1/3] dt-bindings: i2c: spacemit: add optional resets Rob Herring (Arm)
2026-01-08 5:24 ` (subset) [PATCH v3 0/3] i2c: spacemit: add reset support Yixun Lan
-- strict thread matches above, loose matches on Subject: below --
2025-11-19 11:46 [PATCH " Encrow Thorne
2025-11-19 11:46 ` [PATCH 3/3] riscv: dts: spacemit: add reset property Encrow Thorne
2025-11-19 12:10 ` Troy Mitchell
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=aV5r8k4VKnXX_9Sw@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@gentoo.org \
--cc=guodong@riscstar.com \
--cc=jyc0019@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.com \
--cc=troymitchell988@gmail.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