From: Rob Herring <robh@kernel.org>
To: Marcin Sloniewski <marcin.sloniewski@gmail.com>
Cc: heiko.stuebner@theobroma-systems.com, mcoquelin.stm32@gmail.com,
lkundrak@v3.sk, linux-stm32@st-md-mailman.stormreply.com,
alexandre.torgue@st.com, a.fatoum@pengutronix.de,
linus.walleij@linaro.org, allen.chen@ite.com.tw,
linux-arm-kernel@lists.infradead.org, stephan@gerhold.net,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
broonie@kernel.org, mani@kernel.org, sam@ravnborg.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/3] dt-bindings: arm: stm32: document Odyssey compatible
Date: Fri, 31 Jul 2020 13:36:09 -0600 [thread overview]
Message-ID: <20200731193609.GA643298@bogus> (raw)
In-Reply-To: <20200731143053.44866-2-marcin.sloniewski@gmail.com>
On Fri, 31 Jul 2020 16:30:52 +0200, Marcin Sloniewski wrote:
> Document device tree bindings of Seeed SoM and carrier board.
>
> Signed-off-by: Marcin Sloniewski <marcin.sloniewski@gmail.com>
> ---
> Documentation/devicetree/bindings/arm/stm32/stm32.yaml | 6 ++++++
> 1 file changed, 6 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.
next prev parent reply other threads:[~2020-07-31 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 14:30 [PATCH v6 1/3] dt-bindings: vendor-prefixes: add Seeed Studio Marcin Sloniewski
2020-07-31 14:30 ` [PATCH v6 2/3] dt-bindings: arm: stm32: document Odyssey compatible Marcin Sloniewski
2020-07-31 19:36 ` Rob Herring [this message]
2020-07-31 14:30 ` [PATCH v6 3/3] ARM: dts: stm32: add initial support for stm32mp157-odyssey board Marcin Sloniewski
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=20200731193609.GA643298@bogus \
--to=robh@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=alexandre.torgue@st.com \
--cc=allen.chen@ite.com.tw \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko.stuebner@theobroma-systems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lkundrak@v3.sk \
--cc=mani@kernel.org \
--cc=marcin.sloniewski@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=stephan@gerhold.net \
/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;
as well as URLs for NNTP newsgroup(s).