From: patchwork-bot+linux-soc@kernel.org
To: Alexandre TORGUE <alexandre.torgue@foss.st.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] STM32 DT changes for v6.1 #1
Date: Mon, 12 Sep 2022 15:30:25 +0000 [thread overview]
Message-ID: <166299662505.5098.9655726950400940104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <d80afc20-2745-24a2-ab70-a5a03439bd50@foss.st.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Mon, 12 Sep 2022 15:38:44 +0200 you wrote:
> Hi ARM SoC maintainers,
>
> Please consider this first round of STM32 DT updates for v6.1.
>
> Thanks
> Alex
>
> [...]
Here is the summary with links:
- [GIT,PULL] STM32 DT changes for v6.1 #1
https://git.kernel.org/soc/soc/c/6d243f898181
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-09-12 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 13:38 [GIT PULL] STM32 DT changes for v6.1 #1 Alexandre TORGUE
2022-09-12 15:30 ` 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=166299662505.5098.9655726950400940104.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--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