soc.lore.kernel.org archive mirror
 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 update for 6.1
Date: Fri, 23 Sep 2022 16:20:26 +0000	[thread overview]
Message-ID: <166395002683.3905.14181701361161735314.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220918092806.2152700-1-shawnguo@kernel.org>

Hello:

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

On Sun, 18 Sep 2022 17:28:03 +0800 you wrote:
> The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
> 
>   Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-bindings-6.1
> 
> [...]

Here is the summary with links:
  - [GIT,PULL,1/4] i.MX DT bindings update for 6.1
    (no matching commit)
  - [GIT,PULL,2/4] i.MX drivers change for 6.1
    https://git.kernel.org/soc/soc/c/b97e1e2faa3c
  - [GIT,PULL,3/4] i.MX device tree change for 6.1
    (no matching commit)
  - [GIT,PULL,4/4] i.MX arm64 device tree update for 6.1
    (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:[~2022-09-23 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18  9:28 [GIT PULL 1/4] i.MX DT bindings update for 6.1 Shawn Guo
2022-09-18  9:28 ` [GIT PULL 2/4] i.MX drivers change " Shawn Guo
2022-09-18  9:28 ` [GIT PULL 3/4] i.MX device tree " Shawn Guo
2022-09-18  9:28 ` [GIT PULL 4/4] i.MX arm64 device tree update " Shawn Guo
2022-09-23 14:52 ` [GIT PULL 1/4] i.MX DT bindings " patchwork-bot+linux-soc
2022-09-23 16:20 ` 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=166395002683.3905.14181701361161735314.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;
as well as URLs for NNTP newsgroup(s).