From: Shawn Guo <shawnguo@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
David Jander <david@protonic.nl>,
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 v3 2/5] ARM: dts: add Protonic PRTI6Q board
Date: Tue, 21 Apr 2020 12:09:50 +0800 [thread overview]
Message-ID: <20200421040944.GF8571@dragon> (raw)
In-Reply-To: <20200324110432.25062-3-o.rempel@pengutronix.de>
On Tue, Mar 24, 2020 at 12:04:29PM +0100, Oleksij Rempel wrote:
> Protonic PRTI6Q is a development board and a base class for different
> specific customer application boards based on the i.MX6 family of SoCs,
> developed by Protonic Holland.
>
> Signed-off-by: David Jander <david@protonic.nl>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> .../devicetree/bindings/arm/fsl.yaml | 1 +
Have bindings changes (all Protonic compatibles) in a separate patch.
Shawn
next prev parent reply other threads:[~2020-04-21 4:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 11:04 [PATCH v3 0/5] mainline Protonic boards Oleksij Rempel
2020-03-24 11:04 ` [PATCH v3 1/5] dt-bindings: vendor-prefixes: Add an entry for Protonic Holland Oleksij Rempel
2020-03-24 11:04 ` [PATCH v3 2/5] ARM: dts: add Protonic PRTI6Q board Oleksij Rempel
2020-04-21 4:07 ` Shawn Guo
2020-04-21 7:37 ` Oleksij Rempel
2020-04-21 7:39 ` Oleksij Rempel
2020-04-21 4:09 ` Shawn Guo [this message]
2020-03-24 11:04 ` [PATCH v3 3/5] ARM: dts: add Protonic WD2 board Oleksij Rempel
2020-03-24 11:04 ` [PATCH v3 4/5] ARM: dts: add Protonic VT7 board Oleksij Rempel
2020-03-24 11:04 ` [PATCH v3 5/5] ARM: dts: add Protonic RVT board Oleksij Rempel
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=20200421040944.GF8571@dragon \
--to=shawnguo@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 \
/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).