public inbox for soc@kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Yu-Chun Lin <eleanor15x@gmail.com>
Cc: soc@kernel.org
Subject: Re: [PATCH RESEND v3 0/2] arm64: dts: Add support for Kent SoC family
Date: Wed, 28 Jan 2026 22:50:04 +0000	[thread overview]
Message-ID: <176964060486.2263224.2371223213635434331.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260127071530.25426-1-eleanor15x@gmail.com>

Hello:

This series was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Tue, 27 Jan 2026 15:13:59 +0800 you wrote:
> From: Yu-Chun Lin <eleanor.lin@realtek.com>
> 
> Hello,
> 
> This patch series adds initial Device Tree support for Realtek's Kent SoC
> family, including the RTD1501S, RTD1861B, and RTD1920S variants with their
> respective evaluation boards.
> 
> [...]

Here is the summary with links:
  - [RESEND,v3,1/2] dt-bindings: arm: realtek: Add Kent Soc family compatibles
    https://git.kernel.org/soc/soc/c/d83bcab6842f
  - [RESEND,v3,2/2] arm64: dts: realtek: Add Kent SoC and EVB device trees
    https://git.kernel.org/soc/soc/c/b095c27fc874

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-01-28 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  7:13 [PATCH RESEND v3 0/2] arm64: dts: Add support for Kent SoC family Yu-Chun Lin
2026-01-27  7:14 ` [PATCH RESEND v3 1/2] dt-bindings: arm: realtek: Add Kent Soc family compatibles Yu-Chun Lin
2026-01-28 18:35   ` Krzysztof Kozlowski
2026-01-27  7:14 ` [PATCH RESEND v3 2/2] arm64: dts: realtek: Add Kent SoC and EVB device trees Yu-Chun Lin
2026-01-28 18:41   ` Krzysztof Kozlowski
2026-01-28 22:50 ` patchwork-bot+linux-soc [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=176964060486.2263224.2371223213635434331.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=eleanor15x@gmail.com \
    --cc=soc@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