From: patchwork-bot+linux-soc@kernel.org
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] Broadcom devicetree fixes for 5.19
Date: Fri, 24 Jun 2022 16:00:13 +0000 [thread overview]
Message-ID: <165608641381.3411.9550528204633958349.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220620170745.2485199-1-f.fainelli@gmail.com>
Hello:
This pull request was applied to soc/soc.git (arm/fixes)
by Arnd Bergmann <arnd@arndb.de>:
On Mon, 20 Jun 2022 10:07:45 -0700 you wrote:
> The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
>
> Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
>
> are available in the Git repository at:
>
> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.19/devicetree-fixes
>
> [...]
Here is the summary with links:
- [GIT,PULL] Broadcom devicetree fixes for 5.19
https://git.kernel.org/soc/soc/c/b262b3b571bc
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:[~2022-06-24 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 17:07 [GIT PULL] Broadcom devicetree fixes for 5.19 Florian Fainelli
2022-06-24 16:00 ` 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=165608641381.3411.9550528204633958349.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox