From: patchwork-bot+linux-soc@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] RISC-V Devicetree fixes for v6.6-rc3
Date: Tue, 26 Sep 2023 21:21:20 +0000 [thread overview]
Message-ID: <169576328007.24546.200899249000536526.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230916-previous-oversold-9d30891ac6cf@spud>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Sat, 16 Sep 2023 12:40:10 +0100 you wrote:
> Hey Arnd,
>
> Please pull some fixes for the Starfive devicetrees, been sitting around
> since before the mw (but after my last PR), so figured I'd get them out
> sooner rather than later.
>
> Thanks!
>
> [...]
Here is the summary with links:
- [GIT,PULL] RISC-V Devicetree fixes for v6.6-rc3
https://git.kernel.org/soc/soc/c/aab8130550da
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:[~2023-09-26 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 11:40 [GIT PULL] RISC-V Devicetree fixes for v6.6-rc3 Conor Dooley
2023-09-26 21:03 ` patchwork-bot+linux-soc
2023-09-26 21:21 ` 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=169576328007.24546.200899249000536526.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