From: Rob Herring <robh@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
David Jander <david@protonic.nl>, Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: vendor-prefixes: Add an entry for Van der Laan b.v.
Date: Fri, 23 Oct 2020 11:41:02 -0500 [thread overview]
Message-ID: <20201023164102.GA2838572@bogus> (raw)
In-Reply-To: <20201022102733.3277-2-o.rempel@pengutronix.de>
On Thu, 22 Oct 2020 12:27:31 +0200, Oleksij Rempel wrote:
> Add "vdl" entry for Van der Laan b.v.: https://www.teamvdl.nl/
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> 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.
next prev parent reply other threads:[~2020-10-23 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 10:27 [PATCH v4 0/3] mainline LANMCU board Oleksij Rempel
2020-10-22 10:27 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: Add an entry for Van der Laan b.v Oleksij Rempel
2020-10-23 16:41 ` Rob Herring [this message]
2020-10-22 10:27 ` [PATCH v4 2/3] dt-bindings: arm: fsl: add Van der Laan LANMCU board Oleksij Rempel
2020-11-01 8:39 ` Shawn Guo
2020-11-02 9:03 ` Oleksij Rempel
2020-10-22 10:27 ` [PATCH v4 3/3] ARM: dts: " Oleksij Rempel
2020-10-22 11:16 ` 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=20201023164102.GA2838572@bogus \
--to=robh@kernel.org \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).