From: patchwork-bot+linux-soc@kernel.org
To: Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] nuvoton: arm64 devicetree changes for 6.20
Date: Thu, 22 Jan 2026 10:50:06 +0000 [thread overview]
Message-ID: <176907900635.1663980.9486566577842178899.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <0dddb418ec4d81b30e48a079ecad8a388284cb9f.camel@codeconstruct.com.au>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Krzysztof Kozlowski <krzk@kernel.org>:
On Fri, 16 Jan 2026 11:59:01 +1030 you wrote:
> Hello SoC maintainers,
>
> The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
>
> Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
>
> are available in the Git repository at:
>
> [...]
Here is the summary with links:
- [GIT,PULL] nuvoton: arm64 devicetree changes for 6.20
https://git.kernel.org/soc/soc/c/332bd42e2f80
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:[~2026-01-22 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 1:29 [GIT PULL] nuvoton: arm64 devicetree changes for 6.20 Andrew Jeffery
2026-01-22 10:50 ` 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=176907900635.1663980.9486566577842178899.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=andrew@codeconstruct.com.au \
--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