public inbox for soc@kernel.org
 help / color / mirror / Atom feed
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 changes for 6.20
Date: Wed, 21 Jan 2026 16:00:28 +0000	[thread overview]
Message-ID: <176901122809.951664.12786199366366717951.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260120011221.4387-1-shawnguo2@yeah.net>

Hello:

This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Tue, 20 Jan 2026 09:12:14 +0800 you wrote:
> From: Shawn Guo <shawnguo@kernel.org>
> 
> The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
> 
>   Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
> 
> are available in the Git repository at:
> 
> [...]

Here is the summary with links:
  - [GIT,PULL,1/5] i.MX drivers changes for 6.20
    https://git.kernel.org/soc/soc/c/6d9e4c74372b
  - [GIT,PULL,2/5] i.MX dt-bindgings changes for 6.20
    (no matching commit)
  - [GIT,PULL,3/5] i.MX ARM device tree changes for 6.20
    (no matching commit)
  - [GIT,PULL,4/5] i.MX arm64 device tree changes for 6.20
    (no matching commit)
  - [GIT,PULL,5/5] i.MX defconfig changes for 6.20
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-01-21 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20  1:12 [GIT PULL 1/5] i.MX drivers changes for 6.20 Shawn Guo
2026-01-20  1:12 ` [GIT PULL 2/5] i.MX dt-bindgings " Shawn Guo
2026-01-20  1:12 ` [GIT PULL 3/5] i.MX ARM device tree " Shawn Guo
2026-01-20  1:12 ` [GIT PULL 4/5] i.MX arm64 " Shawn Guo
2026-01-20  1:12 ` [GIT PULL 5/5] i.MX defconfig " Shawn Guo
2026-01-21 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=176901122809.951664.12786199366366717951.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