Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Shawn Guo <shawnguo@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/4] i.MX dt-bindings changes for 6.7
Date: Mon, 16 Oct 2023 21:31:57 +0000	[thread overview]
Message-ID: <169749191777.22284.7150829150269000272.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231015132300.2268016-1-shawnguo@kernel.org>

Hello:

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

On Sun, 15 Oct 2023 21:22:57 +0800 you wrote:
> The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
> 
>   Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-bindings-6.7
> 
> [...]

Here is the summary with links:
  - [GIT,PULL,1/4] i.MX dt-bindings changes for 6.7
    https://git.kernel.org/soc/soc/c/6a4347fd674f
  - [GIT,PULL,2/4] i.MX ARM device tree changes for 6.7
    https://git.kernel.org/soc/soc/c/2de3561113f1
  - [GIT,PULL,3/4] i.MX arm64 device tree chanages for 6.7
    https://git.kernel.org/soc/soc/c/1b42ff0c869a
  - [GIT,PULL,4/4] i.MX defconfig changes for 6.7
    (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:[~2023-10-16 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15 13:22 [GIT PULL 1/4] i.MX dt-bindings changes for 6.7 Shawn Guo
2023-10-15 13:22 ` [GIT PULL 2/4] i.MX ARM device tree " Shawn Guo
2023-10-15 13:22 ` [GIT PULL 3/4] i.MX arm64 device tree chanages " Shawn Guo
2023-10-15 13:23 ` [GIT PULL 4/4] i.MX defconfig changes " Shawn Guo
2023-10-16 21:31 ` patchwork-bot+linux-soc [this message]
2023-10-17 22:00 ` [GIT PULL 1/4] i.MX dt-bindings " 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=169749191777.22284.7150829150269000272.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=shawnguo@kernel.org \
    --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