From: patchwork-bot+linux-soc@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] RISC-V firmware drivers for v6.9
Date: Wed, 06 Mar 2024 07:00:30 +0000 [thread overview]
Message-ID: <170970843042.7525.14145405596772069767.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240305-vicinity-dumpling-8943ef26f004@spud>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Tue, 5 Mar 2024 20:00:42 +0000 you wrote:
> Hey Arnd,
>
> Feel free to cherry pick this either if it makes more sense (or even
> send it to fixes instead). It's a fix for an oversize allocation, so
> given how late it is in the merge window I opted to send it as 6.9
> material.
>
> [...]
Here is the summary with links:
- [GIT,PULL] RISC-V firmware drivers for v6.9
https://git.kernel.org/soc/soc/c/1c7cfb6158f6
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:[~2024-03-06 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 20:00 [GIT PULL] RISC-V firmware drivers for v6.9 Conor Dooley
2024-03-06 7:00 ` patchwork-bot+linux-soc
2024-03-06 7:00 ` 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=170970843042.7525.14145405596772069767.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).