From: patchwork-bot+linux-soc@kernel.org
To: Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] nuvoton: early devicetree changes for 6.18
Date: Mon, 01 Sep 2025 10:59:20 +0000 [thread overview]
Message-ID: <175672436025.3681523.5852506565913716862.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5e7e5d2cedb3bb232420ad720c857b95d8c02f21.camel@codeconstruct.com.au>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Mon, 25 Aug 2025 11:19:10 +0930 you wrote:
> Hello SoC maintainers,
>
> The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
>
> Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
>
> are available in the Git repository at:
>
> [...]
Here is the summary with links:
- [GIT,PULL] nuvoton: early devicetree changes for 6.18
https://git.kernel.org/soc/soc/c/921e41c4465e
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-09-01 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 1:49 [GIT PULL] nuvoton: early devicetree changes for 6.18 Andrew Jeffery
2025-09-01 10:59 ` 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=175672436025.3681523.5852506565913716862.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 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.