From: "Rob Herring (Arm)" <robh@kernel.org>
To: "Goran Rađenović" <goran.radni@gmail.com>
Cc: "Goran Rađenović" <gradenovic@ultratronik.de>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
linux-stm32@st-md-mailman.stormreply.com,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
"Conor Dooley" <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] dt-bindings: arm: stm32: Document Ultratronik's Fly board DT binding
Date: Tue, 25 Mar 2025 10:05:38 -0500 [thread overview]
Message-ID: <174291508527.2051452.5158369080088647376.robh@kernel.org> (raw)
In-Reply-To: <20250325110409.2323611-3-goran.radni@gmail.com>
On Tue, 25 Mar 2025 12:04:06 +0100, Goran Rađenović wrote:
> From: Goran Rađenović <gradenovic@ultratronik.de>
>
> This commit documents ultra-fly-sbc devicetree binding based on
> STM32MP157 SoC.
>
> Signed-off-by: Goran Rađenović <goran.radni@gmail.com>
> ---
> Documentation/devicetree/bindings/arm/stm32/stm32.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
Missing tags:
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-03-25 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250325110409.2323611-1-goran.radni@gmail.com>
2025-03-25 11:04 ` [PATCH v3 2/3] dt-bindings: arm: stm32: Document Ultratronik's Fly board DT binding Goran Rađenović
2025-03-25 15:05 ` Rob Herring (Arm) [this message]
2025-03-26 7:41 ` Krzysztof Kozlowski
2025-03-25 11:04 ` [PATCH v3 3/3] ARM: dts: stm32: add initial support for stm32mp157-ultra-fly-sbc board Goran Rađenović
2025-03-26 7:41 ` Krzysztof Kozlowski
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=174291508527.2051452.5158369080088647376.robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=goran.radni@gmail.com \
--cc=gradenovic@ultratronik.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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