From: patchwork-bot+linux-soc@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/3] RISC-V config for v6.16
Date: Wed, 21 May 2025 21:30:47 +0000 [thread overview]
Message-ID: <174786304703.2284637.5221097862408867704.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250516-joystick-mortified-385820b1ad0b@spud>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Fri, 16 May 2025 11:36:53 +0100 you wrote:
> Hey Arnd,
>
> These are a bit late, but I was waiting for some acks on patches that
> were outstanding for a while dts wise.
>
> Cheers,
> Conor.
>
> [...]
Here is the summary with links:
- [GIT,PULL,1/3] RISC-V config for v6.16
(no matching commit)
- [GIT,PULL,2/3] RISC-V cache drivers for v6.16
https://git.kernel.org/soc/soc/c/07a3c038bd9c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-05-21 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 10:36 [GIT PULL 1/3] RISC-V config for v6.16 Conor Dooley
2025-05-21 21:30 ` patchwork-bot+linux-soc [this message]
2025-05-22 11:20 ` patchwork-bot+linux-soc
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=174786304703.2284637.5221097862408867704.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