From: patchwork-bot+linux-soc@kernel.org
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: soc@kernel.org
Subject: Re: [GIT,PULL,1/4] MediaTek arm32 updates for v6.17
Date: Tue, 22 Jul 2025 20:50:54 +0000 [thread overview]
Message-ID: <175321745482.949540.17137010341068655771.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250711083656.33538-1-angelogioacchino.delregno@collabora.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Fri, 11 Jul 2025 10:36:45 +0200 you wrote:
> The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
>
> Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git tags/mtk-arm32-for-v6.17
>
> [...]
Here is the summary with links:
- [GIT,PULL,1/4] MediaTek arm32 updates for v6.17
https://git.kernel.org/soc/soc/c/73bcce043f3c
- [GIT,PULL,2/4] MediaTek ARM32 DTS updates for v6.17
(no matching commit)
- [GIT,PULL,3/4] MediaTek ARM64 DTS updates for v6.17
(no matching commit)
- [GIT,PULL,4/4] MediaTek driver updates for v6.17
(no matching commit)
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-07-22 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 8:36 [GIT,PULL,1/4] MediaTek arm32 updates for v6.17 AngeloGioacchino Del Regno
2025-07-11 8:36 ` [GIT,PULL,2/4] MediaTek ARM32 DTS " AngeloGioacchino Del Regno
2025-07-11 8:36 ` [GIT,PULL,3/4] MediaTek ARM64 " AngeloGioacchino Del Regno
2025-07-11 8:36 ` [GIT,PULL,4/4] MediaTek driver " AngeloGioacchino Del Regno
2025-07-21 15:32 ` [GIT,PULL,1/4] MediaTek arm32 " patchwork-bot+linux-soc
2025-07-22 20:50 ` 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=175321745482.949540.17137010341068655771.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=angelogioacchino.delregno@collabora.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