From: patchwork-bot+linux-soc@kernel.org
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/2] Broadcom devicetree changes for 7.1
Date: Wed, 01 Apr 2026 21:50:31 +0000 [thread overview]
Message-ID: <177508023178.3876275.6579807299020012098.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260323190239.1890505-1-florian.fainelli@broadcom.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Mon, 23 Mar 2026 12:02:38 -0700 you wrote:
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>
> Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>
> are available in the Git repository at:
>
> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.1/devicetree
>
> [...]
Here is the summary with links:
- [GIT,PULL,1/2] Broadcom devicetree changes for 7.1
(no matching commit)
- [GIT,PULL,2/2] Broadcom devicetree-arm64 changes for 7.1
https://git.kernel.org/soc/soc/c/185fb140508b
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:[~2026-04-01 21:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 19:02 [GIT PULL 1/2] Broadcom devicetree changes for 7.1 Florian Fainelli
2026-03-23 19:02 ` [GIT PULL 2/2] Broadcom devicetree-arm64 " Florian Fainelli
2026-04-01 11:18 ` Krzysztof Kozlowski
2026-04-01 12:02 ` Krzysztof Kozlowski
2026-04-01 14:37 ` Arnd Bergmann
2026-04-01 14:47 ` Krzysztof Kozlowski
2026-04-01 16:33 ` Arnd Bergmann
2026-04-01 16:38 ` Krzysztof Kozlowski
2026-04-01 16:41 ` Florian Fainelli
2026-04-01 16:49 ` Mark Brown
2026-04-01 16:50 ` Arnd Bergmann
2026-03-27 11:53 ` [GIT PULL 1/2] Broadcom devicetree " Krzysztof Kozlowski
2026-03-27 16:26 ` Florian Fainelli
2026-04-01 21:50 ` patchwork-bot+linux-soc [this message]
2026-04-01 22:12 ` Arnd Bergmann
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=177508023178.3876275.6579807299020012098.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