From: patchwork-bot+linux-soc@kernel.org
To: Yixun Lan <dlan@gentoo.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] RISC-V SpacemiT Devicetrees for v6.16
Date: Wed, 21 May 2025 22:31:49 +0000 [thread overview]
Message-ID: <174786670948.2299459.12403321460401196270.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250514044841-GYA524674@gentoo>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 14 May 2025 04:48:41 +0000 you wrote:
> Hi Arnd,
>
> Please pull SpacemiT's device tree changes for v6.16, thanks
>
> Please note, there are clock dt-binding dependencies which also included
> in this PR, they are exactly same commits (same hash) which already queued
> at clock's tree[1].
>
> [...]
Here is the summary with links:
- [GIT,PULL] RISC-V SpacemiT Devicetrees for v6.16
https://git.kernel.org/soc/soc/c/ba32d96e90c1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-05-21 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 4:48 [GIT PULL] RISC-V SpacemiT Devicetrees for v6.16 Yixun Lan
2025-05-14 4:48 ` Yixun Lan
2025-05-21 22:31 ` 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=174786670948.2299459.12403321460401196270.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=dlan@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.