From: patchwork-bot+linux-soc@kernel.org
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/4] Broadcom devicetree changes for 6.4
Date: Fri, 14 Apr 2023 13:10:30 +0000 [thread overview]
Message-ID: <168147783056.23940.12465243925313520851.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230410232606.1917803-1-f.fainelli@gmail.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Mon, 10 Apr 2023 16:26:03 -0700 you wrote:
> The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
>
> Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
>
> are available in the Git repository at:
>
> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.4/devicetree
>
> [...]
Here is the summary with links:
- [GIT,PULL,1/4] Broadcom devicetree changes for 6.4
(no matching commit)
- [GIT,PULL,2/4] Broadcom devicetree-arm64 changes for 6.4
(no matching commit)
- [GIT,PULL,3/4] Broadcom drivers changes for 6.4
https://git.kernel.org/soc/soc/c/3ac02aa53d60
- [GIT,PULL,4/4] Broadcom soc changes for 6.4
https://git.kernel.org/soc/soc/c/3e54e7c8c42a
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:[~2023-04-14 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 23:26 [GIT PULL 1/4] Broadcom devicetree changes for 6.4 Florian Fainelli
2023-04-10 23:26 ` Florian Fainelli
2023-04-10 23:26 ` [GIT PULL 2/4] Broadcom devicetree-arm64 " Florian Fainelli
2023-04-10 23:26 ` Florian Fainelli
2023-04-10 23:26 ` [GIT PULL 3/4] Broadcom drivers " Florian Fainelli
2023-04-10 23:26 ` Florian Fainelli
2023-04-10 23:26 ` [GIT PULL 4/4] Broadcom soc " Florian Fainelli
2023-04-10 23:26 ` Florian Fainelli
2023-04-14 13:10 ` patchwork-bot+linux-soc [this message]
2023-04-14 16:21 ` [GIT PULL 1/4] Broadcom devicetree " 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=168147783056.23940.12465243925313520851.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=f.fainelli@gmail.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 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.