From: patchwork-bot+linux-soc@kernel.org
To: Shawn Guo <shawnguo2@yeah.net>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/5] i.MX drivers update for 6.19
Date: Fri, 21 Nov 2025 21:50:10 +0000 [thread overview]
Message-ID: <176376181024.2598359.1757506004654702538.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251117123358.2009662-1-shawnguo2@yeah.net>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Mon, 17 Nov 2025 20:33:47 +0800 you wrote:
> From: Shawn Guo <shawnguo@kernel.org>
>
> The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
>
> Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
>
> are available in the Git repository at:
>
> [...]
Here is the summary with links:
- [GIT,PULL,1/5] i.MX drivers update for 6.19
(no matching commit)
- [GIT,PULL,2/5] i.MX dt-bindings update for 6.19
https://git.kernel.org/soc/soc/c/a60997452ac8
- [GIT,PULL,3/5] i.MX ARM device tree changes for 6.19
(no matching commit)
- [GIT,PULL,4/5] i.MX arm64 device tree changes for 6.19
(no matching commit)
- [GIT,PULL,5/5] i.MX defconfig changes for 6.19
(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-11-21 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 12:33 [GIT PULL 1/5] i.MX drivers update for 6.19 Shawn Guo
2025-11-17 12:33 ` [GIT PULL 2/5] i.MX dt-bindings " Shawn Guo
2025-11-17 12:33 ` [GIT PULL 3/5] i.MX ARM device tree changes " Shawn Guo
2025-11-17 12:33 ` [GIT PULL 4/5] i.MX arm64 " Shawn Guo
2025-11-17 12:33 ` [GIT PULL 5/5] i.MX defconfig " Shawn Guo
2025-11-21 20:21 ` [GIT PULL 1/5] i.MX drivers update " patchwork-bot+linux-soc
2025-11-21 20:50 ` patchwork-bot+linux-soc
2025-11-21 21:50 ` patchwork-bot+linux-soc [this message]
2025-11-25 13:50 ` 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=176376181024.2598359.1757506004654702538.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=shawnguo2@yeah.net \
--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