From: patchwork-bot+linux-soc@kernel.org
To: Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: soc@kernel.org
Subject: Re: [PATCH] dt-bindings: clock: stm32mp1: adapt example for "st,stm32mp1-rcc-secure"
Date: Fri, 13 May 2022 10:00:18 +0000 [thread overview]
Message-ID: <165243601831.30999.161396984094001630.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220511092559.4952-1-alexandre.torgue@foss.st.com>
Hello:
This patch was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 11 May 2022 11:25:59 +0200 you wrote:
> For "st,stm32mp1-rcc-secure" schema, clocks and clock-names entries are now
> required properties.
>
> Signed-off-by: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Acked-by: Rob Herring <robh@kernel.org>
>
>
> [...]
Here is the summary with links:
- dt-bindings: clock: stm32mp1: adapt example for "st,stm32mp1-rcc-secure"
https://git.kernel.org/soc/soc/c/045d0c3db911
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:[~2022-05-13 10:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 9:25 [PATCH] dt-bindings: clock: stm32mp1: adapt example for "st,stm32mp1-rcc-secure" Alexandre Torgue
2022-05-11 9:25 ` [PATCH] dt-bindings: clock: stm32mp1: adapt example for "st, stm32mp1-rcc-secure" Alexandre Torgue
2022-05-13 10:00 ` patchwork-bot+linux-soc [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-09 13:46 Alexandre Torgue
2022-05-09 13:46 ` [PATCH] dt-bindings: clock: stm32mp1: adapt example for "st,stm32mp1-rcc-secure" Alexandre Torgue
2022-05-09 19:16 ` [PATCH] dt-bindings: clock: stm32mp1: adapt example for "st, stm32mp1-rcc-secure" Rob Herring
2022-05-09 19:16 ` [PATCH] dt-bindings: clock: stm32mp1: adapt example for "st,stm32mp1-rcc-secure" Rob Herring
2022-05-10 7:47 ` Alexandre TORGUE
2022-05-10 7:47 ` Alexandre TORGUE
2022-05-10 14:57 ` Rob Herring
2022-05-10 14:57 ` Rob Herring
2022-05-10 16:44 ` Alexandre TORGUE
2022-05-10 16:44 ` Alexandre TORGUE
2022-05-10 18:22 ` Rob Herring
2022-05-10 18:22 ` Rob Herring
2022-05-10 18:23 ` Rob Herring
2022-05-10 18:23 ` Rob Herring
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=165243601831.30999.161396984094001630.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 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.