From: patchwork-bot+linux-soc@kernel.org
To: Chen-Yu Tsai <wens@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] Allwinner SoC device tree changes for 6.11 part 2
Date: Fri, 12 Jul 2024 10:20:30 +0000 [thread overview]
Message-ID: <172077963092.4770.571058674159686915.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Zo7O73Afx7lZcBRi@wens.tw>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Thu, 11 Jul 2024 02:11:59 +0800 you wrote:
> Hi Arnd,
>
> Here's a late DT commit for 6.11. The driver parts of the H616 crypto
> engine series was only merged last week, so I only got to it today.
>
> The whole series has been tested by multiple people including me, so
> I don't expect any issues. And it's just enabling a new IP block.
>
> [...]
Here is the summary with links:
- [GIT,PULL] Allwinner SoC device tree changes for 6.11 part 2
https://git.kernel.org/soc/soc/c/48d224558645
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-07-12 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 18:11 [GIT PULL] Allwinner SoC device tree changes for 6.11 part 2 Chen-Yu Tsai
2024-07-12 10:20 ` 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=172077963092.4770.571058674159686915.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=soc@kernel.org \
--cc=wens@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.