Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] RISC-V devicetrees for v7.3 - Early Canaan k230 material
Date: Fri, 24 Jul 2026 16:40:22 +0000	[thread overview]
Message-ID: <178491122238.3229915.5266351534692676918.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260710-purge-scarcity-942f27750ce1@spud>

Hello:

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

On Fri, 10 Jul 2026 19:25:00 +0100 you wrote:
> Hey folks,
> 
> Please pull an early tag with the Canaan k230 support that I was too late
> with for the 7.2 merge window. Some of these patches date from 2024, so I
> have elected not to squash or have the submitters of the clock changes etc
> resubmit the original k230 series with their stuff squashed in so that
> the history of the initial bring-up is retained, particularly given
> Yangyu's detailed commit message in "riscv: dts: add initial canmv-k230
> and k230-evb dts" that covers the testing done and decisions made about
> supporting the standard Svpbmt extension or T-Head custom MAEE stuff etc.
> 
> [...]

Here is the summary with links:
  - [GIT,PULL] RISC-V devicetrees for v7.3 - Early Canaan k230 material
    https://git.kernel.org/soc/soc/c/0bcfbb1f786d

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



      reply	other threads:[~2026-07-24 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 18:25 [GIT PULL] RISC-V devicetrees for v7.3 - Early Canaan k230 material Conor Dooley
2026-07-24 16:40 ` 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=178491122238.3229915.5266351534692676918.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=conor@kernel.org \
    --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