From: patchwork-bot+linux-soc@kernel.org
To: Tony Lindgren <tony@atomide.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/4] Maintainaer updates for omaps
Date: Tue, 03 May 2022 14:50:21 +0000 [thread overview]
Message-ID: <165158942185.22061.5061851583312510016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pull-1651061256-836848@atomide.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 27 Apr 2022 15:08:25 +0300 you wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
>
> Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
>
> are available in the Git repository at:
>
> [...]
Here is the summary with links:
- [GIT,PULL,1/4] Maintainaer updates for omaps
https://git.kernel.org/soc/soc/c/211e1faef5a0
- [GIT,PULL,2/4] Defconfig changes for omaps
https://git.kernel.org/soc/soc/c/efad535480c1
- [GIT,PULL,3/4] SoC clean-up for omaps
https://git.kernel.org/soc/soc/c/89c839720c9b
- [GIT,PULL,4/4] Drivers changes for ti-sysc
https://git.kernel.org/soc/soc/c/4d7b3fd9f38f
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:[~2022-05-03 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 12:08 [GIT PULL 1/4] Maintainaer updates for omaps Tony Lindgren
2022-04-27 12:08 ` Tony Lindgren
2022-04-27 12:08 ` [GIT PULL 2/4] Defconfig changes " Tony Lindgren
2022-04-27 12:08 ` Tony Lindgren
2022-04-27 12:08 ` [GIT PULL 3/4] SoC clean-up " Tony Lindgren
2022-04-27 12:08 ` Tony Lindgren
2022-04-27 12:08 ` [GIT PULL 4/4] Drivers changes for ti-sysc Tony Lindgren
2022-04-27 12:08 ` Tony Lindgren
2022-05-03 14:50 ` 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=165158942185.22061.5061851583312510016.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 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.