From: patchwork-bot+linux-soc@kernel.org
To: Tony Lindgren <tony@atomide.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/4] Devicetree binding changes for omaps for v6.6
Date: Sat, 12 Aug 2023 09:14:49 +0000 [thread overview]
Message-ID: <169183168903.30475.4757958438793662508.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pull-1691658952-110529@atomide.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Thu, 10 Aug 2023 12:16:50 +0300 you wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> 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] Devicetree binding changes for omaps for v6.6
https://git.kernel.org/soc/soc/c/4e62609005c3
- [GIT,PULL,2/4] Maintainer file list update for omaps for v6.6
(no matching commit)
- [GIT,PULL,3/4] Devicetree changes for omaps for v6.6
https://git.kernel.org/soc/soc/c/064a805c4aa8
- [GIT,PULL,4/4] SoC changes for omaps for v6.6
https://git.kernel.org/soc/soc/c/c0c3bf74242a
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:[~2023-08-12 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 9:16 [GIT PULL 1/4] Devicetree binding changes for omaps for v6.6 Tony Lindgren
2023-08-10 9:16 ` [GIT PULL 2/4] Maintainer file list update " Tony Lindgren
2023-08-10 9:16 ` [GIT PULL 3/4] Devicetree changes " Tony Lindgren
2023-08-10 9:16 ` [GIT PULL 4/4] SoC " Tony Lindgren
2023-08-12 9:14 ` patchwork-bot+linux-soc [this message]
2023-08-12 12:50 ` [GIT PULL 1/4] Devicetree binding " 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=169183168903.30475.4757958438793662508.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=soc@kernel.org \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox