From: patchwork-bot+linux-soc@kernel.org
To: Michal Simek <monstr@monstr.eu>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] arm64: ZynqMP SoC changes for v6.15
Date: Thu, 20 Mar 2025 17:10:46 +0000 [thread overview]
Message-ID: <174249064694.1843567.17987656430600336319.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CAHTX3d+T+_zvwAVqGO+J_+Yia+wXAGsaEbPi1ye1AUYXoq6dmw@mail.gmail.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Fri, 14 Mar 2025 16:05:32 +0100 you wrote:
> Hi,
>
> please pull this patch to your tree. Tree is based on v6.13-rc1 but
> that shouldn't be a problem.
> There is no conflict with the latest Linus tree and also don't see any
> issue with Linux next.
> The patch is pretty much cleanup because firmware is not using that
> parameters anyway.
>
> [...]
Here is the summary with links:
- [GIT,PULL] arm64: ZynqMP SoC changes for v6.15
https://git.kernel.org/soc/soc/c/2124055fb5c6
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-03-20 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 15:05 [GIT PULL] arm64: ZynqMP SoC changes for v6.15 Michal Simek
2025-03-20 17:10 ` 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=174249064694.1843567.17987656430600336319.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=monstr@monstr.eu \
--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