From: Rob Herring <robh@kernel.org>
To: Marcin Sloniewski <marcin.sloniewski@gmail.com>
Cc: a.fatoum@pengutronix.de, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mani@kernel.org,
mcoquelin.stm32@gmail.com, alexandre.torgue@st.com,
sam@ravnborg.org, allen.chen@ite.com.tw, robh+dt@kernel.org,
stephan@gerhold.net, broonie@kernel.org,
linus.walleij@linaro.org, devicetree@vger.kernel.org,
heiko.stuebner@theobroma-systems.com, lkundrak@v3.sk,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v2 1/3] dt-bindings: vendor-prefixes: add Seeed Studio
Date: Tue, 21 Jul 2020 10:02:49 -0600 [thread overview]
Message-ID: <20200721160249.GA377907@bogus> (raw)
In-Reply-To: <20200721152015.11608-1-marcin.sloniewski@gmail.com>
On Tue, 21 Jul 2020 17:20:13 +0200, Marcin Sloniewski wrote:
> Add the "seeed" vendor prefix for Seeed Technology Co., Ltd
> Website: https://www.seeedstudio.com/
>
> Signed-off-by: Marcin Sloniewski <marcin.sloniewski@gmail.com>
> Acked-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 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.
prev parent reply other threads:[~2020-07-21 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 15:20 [PATCH v2 1/3] dt-bindings: vendor-prefixes: add Seeed Studio Marcin Sloniewski
2020-07-21 15:20 ` [PATCH v2 2/3] dt-bindings: arm: stm32: document Odyssey compatible Marcin Sloniewski
2020-07-21 15:20 ` [PATCH v2 3/3] ARM: dts: stm32: add initial support for stm32mp157-odyssey board Marcin Sloniewski
2020-07-21 15:48 ` Ahmad Fatoum
2020-07-21 16:06 ` Alexandre Torgue
2020-07-21 16:02 ` Rob Herring [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=20200721160249.GA377907@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).