From: patchwork-bot+linux-soc@kernel.org
To: Tony Lindgren <tony@atomide.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] More devicetree changes for omaps
Date: Thu, 05 May 2022 19:31:47 +0000 [thread overview]
Message-ID: <165177910793.9627.18392030272831655745.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pull-1651726643-535261@atomide.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Thu, 5 May 2022 07:58:12 +0300 you wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit dff844e1fe17e6c41e5899d46a378f857ea4f354:
>
> ARM: dts: am335x-baltos: update MPU regulator range (2022-04-21 14:12:52 +0300)
>
> are available in the Git repository at:
>
> [...]
Here is the summary with links:
- [GIT,PULL] More devicetree changes for omaps
https://git.kernel.org/soc/soc/c/485b5afae681
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-05 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 4:58 [GIT PULL] More devicetree changes for omaps Tony Lindgren
2022-05-05 19:31 ` 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=165177910793.9627.18392030272831655745.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