From: patchwork-bot+linux-soc@kernel.org
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/4] Broadcom defconfig-arm64 changes for 6.18
Date: Mon, 15 Sep 2025 13:50:42 +0000 [thread overview]
Message-ID: <175794424250.4179625.12284555588564912705.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250910171910.666401-1-florian.fainelli@broadcom.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 10 Sep 2025 10:19:07 -0700 you wrote:
> The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
>
> Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
>
> are available in the Git repository at:
>
> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.18/defconfig-arm64
>
> [...]
Here is the summary with links:
- [GIT,PULL,1/4] Broadcom defconfig-arm64 changes for 6.18
(no matching commit)
- [GIT,PULL,2/4] Broadcom devicetree changes for 6.18
(no matching commit)
- [GIT,PULL,3/4] Broadcom devicetree-arm64 changes for 6.18
https://git.kernel.org/soc/soc/c/41d773149b88
- [GIT,PULL,4/4] Broadcom drivers changes for 6.18
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-15 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 17:19 [GIT PULL 1/4] Broadcom defconfig-arm64 changes for 6.18 Florian Fainelli
2025-09-10 17:19 ` [GIT PULL 2/4] Broadcom devicetree " Florian Fainelli
2025-09-10 17:19 ` [GIT PULL 3/4] Broadcom devicetree-arm64 " Florian Fainelli
2025-09-10 17:19 ` [GIT PULL 4/4] Broadcom drivers " Florian Fainelli
2025-09-15 13:50 ` patchwork-bot+linux-soc [this message]
2025-09-15 14:30 ` [GIT PULL 1/4] Broadcom defconfig-arm64 " patchwork-bot+linux-soc
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=175794424250.4179625.12284555588564912705.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=florian.fainelli@broadcom.com \
--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