From: patchwork-bot+linux-soc@kernel.org
To: Thierry Reding <thierry.reding@gmail.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/4] soc/tegra: Changes for v6.6-rc1
Date: Sat, 12 Aug 2023 10:20:27 +0000 [thread overview]
Message-ID: <169183562771.32343.6324752498558311561.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230728094129.3587109-1-thierry.reding@gmail.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Fri, 28 Jul 2023 11:41:25 +0200 you wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
>
> Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
>
> are available in the Git repository at:
>
> [...]
Here is the summary with links:
- [GIT,PULL,1/4] soc/tegra: Changes for v6.6-rc1
https://git.kernel.org/soc/soc/c/eb865fd2fdef
- [GIT,PULL,2/4] dt-bindings: Changes for v6.6-rc1
(no matching commit)
- [GIT,PULL,3/4] ARM: tegra: Device tree changes for v6.6-rc1
(no matching commit)
- [GIT,PULL,4/4] arm64: tegra: Device tree changes for v6.6-rc1
(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:[~2023-08-12 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 9:41 [GIT PULL 1/4] soc/tegra: Changes for v6.6-rc1 Thierry Reding
2023-07-28 9:41 ` Thierry Reding
2023-07-28 9:41 ` [GIT PULL 2/4] dt-bindings: " Thierry Reding
2023-07-28 9:41 ` Thierry Reding
2023-07-28 9:41 ` [GIT PULL 3/4] ARM: tegra: Device tree changes " Thierry Reding
2023-07-28 9:41 ` Thierry Reding
2023-07-28 9:41 ` [GIT PULL 4/4] arm64: " Thierry Reding
2023-07-28 9:41 ` Thierry Reding
2023-08-12 9:14 ` [GIT PULL 1/4] soc/tegra: Changes " patchwork-bot+linux-soc
2023-08-12 10: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=169183562771.32343.6324752498558311561.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=soc@kernel.org \
--cc=thierry.reding@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.