From: Rob Herring <robh@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Oleksij Rempel <o.rempel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/5] dt-bindings: vendor-prefixes: Add an entry for Protonic Holland
Date: Fri, 10 Apr 2020 12:14:05 -0500 [thread overview]
Message-ID: <20200410171405.GA11823@bogus> (raw)
In-Reply-To: <20200330120640.9810-2-o.rempel@pengutronix.de>
On Mon, 30 Mar 2020 14:06:36 +0200, Oleksij Rempel wrote:
> Add "prt" entry for Protonic Holland: https://www.protonic.nl/en/
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Applied, thanks.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH v4 1/5] dt-bindings: vendor-prefixes: Add an entry for Protonic Holland
Date: Fri, 10 Apr 2020 12:14:05 -0500 [thread overview]
Message-ID: <20200410171405.GA11823@bogus> (raw)
In-Reply-To: <20200330120640.9810-2-o.rempel@pengutronix.de>
On Mon, 30 Mar 2020 14:06:36 +0200, Oleksij Rempel wrote:
> Add "prt" entry for Protonic Holland: https://www.protonic.nl/en/
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Applied, thanks.
Rob
next prev parent reply other threads:[~2020-04-10 17:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 12:06 [PATCH v4 0/5] mainline Protonic boards Oleksij Rempel
2020-03-30 12:06 ` Oleksij Rempel
2020-03-30 12:06 ` [PATCH v4 1/5] dt-bindings: vendor-prefixes: Add an entry for Protonic Holland Oleksij Rempel
2020-03-30 12:06 ` Oleksij Rempel
2020-04-10 17:14 ` Rob Herring [this message]
2020-04-10 17:14 ` Rob Herring
2020-03-30 12:06 ` [PATCH v4 2/5] ARM: dts: add Protonic PRTI6Q board Oleksij Rempel
2020-03-30 12:06 ` Oleksij Rempel
2020-04-10 17:18 ` Rob Herring
2020-04-10 17:18 ` Rob Herring
2020-03-30 12:06 ` [PATCH v4 3/5] ARM: dts: add Protonic WD2 board Oleksij Rempel
2020-03-30 12:06 ` Oleksij Rempel
2020-04-10 17:20 ` Rob Herring
2020-04-10 17:20 ` Rob Herring
2020-03-30 12:06 ` [PATCH v4 4/5] ARM: dts: add Protonic VT7 board Oleksij Rempel
2020-03-30 12:06 ` Oleksij Rempel
2020-04-10 17:21 ` Rob Herring
2020-04-10 17:21 ` Rob Herring
2020-03-30 12:06 ` [PATCH v4 5/5] ARM: dts: add Protonic RVT board Oleksij Rempel
2020-03-30 12:06 ` Oleksij Rempel
2020-04-10 17:23 ` Rob Herring
2020-04-10 17: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=20200410171405.GA11823@bogus \
--to=robh@kernel.org \
--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 \
/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.