From: patchwork-bot+linux-soc@kernel.org
To: Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] aspeed: First batch of devicetree changes for 6.19
Date: Fri, 21 Nov 2025 20:22:07 +0000 [thread overview]
Message-ID: <176375652799.2571237.16413645923366843407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <d2bd7e3e6045ac68875fd220e528c76f4fb2faac.camel@codeconstruct.com.au>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Fri, 31 Oct 2025 09:40:25 +1030 you wrote:
> Hello SoC maintainers,
>
> The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
>
> Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
>
> are available in the Git repository at:
>
> [...]
Here is the summary with links:
- [GIT,PULL] aspeed: First batch of devicetree changes for 6.19
https://git.kernel.org/soc/soc/c/7ab4745858cf
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-11-21 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 23:10 [GIT PULL] aspeed: First batch of devicetree changes for 6.19 Andrew Jeffery
2025-11-21 20:22 ` 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=176375652799.2571237.16413645923366843407.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.