Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Troy Mitchell <troy.mitchell@linux.spacemit.com>
To: Alex Elder <elder@riscstar.com>, broonie@kernel.org, dlan@gentoo.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-spi@vger.kernel.org,
	spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Conor Dooley <conor.dooley@microchip.com>,
	Troy Mitchell <troy.mitchell@linux.spacemit.com>
Subject: Re: [PATCH v6 1/3] dt-bindings: spi: add SpacemiT K1 SPI support
Date: Tue, 28 Oct 2025 09:40:34 +0800	[thread overview]
Message-ID: <3B5AA5AFF5C53D64+aQAfEn1OBGmevjfS@kernel.org> (raw)
In-Reply-To: <20251027125504.297033-2-elder@riscstar.com>

On Mon, Oct 27, 2025 at 07:55:01AM -0500, Alex Elder wrote:
> Add support for the SPI controller implemented by the SpacemiT K1 SoC.
> 
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
Acked-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-10-28  1:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 12:55 [PATCH v6 0/3] spi: support the SpacemiT K1 SPI controller Alex Elder
2025-10-27 12:55 ` [PATCH v6 1/3] dt-bindings: spi: add SpacemiT K1 SPI support Alex Elder
2025-10-28  1:40   ` Troy Mitchell [this message]
2025-10-27 12:55 ` [PATCH v6 2/3] spi: spacemit: introduce SpacemiT K1 SPI controller driver Alex Elder
2025-10-28  1:46   ` Troy Mitchell
2025-11-14 20:37     ` Alex Elder
2025-10-30 20:45   ` kernel test robot
2025-10-30 21:49   ` kernel test robot
2025-10-27 12:55 ` [PATCH v6 3/3] riscv: dts: spacemit: define a SPI controller node Alex Elder
2025-10-27 14:40 ` [PATCH v6 0/3] spi: support the SpacemiT K1 SPI controller Mark Brown
2025-10-28 12:13   ` Alex Elder

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=3B5AA5AFF5C53D64+aQAfEn1OBGmevjfS@kernel.org \
    --to=troy.mitchell@linux.spacemit.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@gentoo.org \
    --cc=elder@riscstar.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=spacemit@lists.linux.dev \
    /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