From: Shawn Guo <shawnguo@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Li Yang <leoyang.li@nxp.com>
Subject: Re: [PATCH devicetree 1/2] dt-bindings: arm: fsl: document the LX2160A BlueBox 3 boards
Date: Mon, 4 Oct 2021 11:48:16 +0800 [thread overview]
Message-ID: <20211004034815.GC15650@dragon> (raw)
In-Reply-To: <20210827202722.2567687-1-vladimir.oltean@nxp.com>
On Fri, Aug 27, 2021 at 11:27:21PM +0300, Vladimir Oltean wrote:
> Document the compatible string for the LX2160A system that is part of
> the BlueBox 3. Also add a separate compatible string for Rev A, since
> technically it uses a different device tree.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
> ---
> Documentation/devicetree/bindings/arm/fsl.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
> index 60f4862ba15e..d31464df987d 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> @@ -979,6 +979,8 @@ properties:
> - enum:
> - fsl,lx2160a-qds
> - fsl,lx2160a-rdb
> + - fsl,lx2160a-bluebox3
> + - fsl,lx2160a-bluebox3-rev-a
It would be nice to keep them alphabetically sorted. I fixed it up and
applied the patch.
Shawn
> - fsl,lx2162a-qds
> - const: fsl,lx2160a
>
> --
> 2.25.1
>
prev parent reply other threads:[~2021-10-04 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 20:27 [PATCH devicetree 1/2] dt-bindings: arm: fsl: document the LX2160A BlueBox 3 boards Vladimir Oltean
2021-08-27 20:27 ` [PATCH devicetree 2/2] arm64: dts: add device tree for the LX2160A on the NXP BlueBox3 board Vladimir Oltean
2021-08-28 1:38 ` Li Yang
2021-10-04 3:43 ` Shawn Guo
2021-08-31 21:23 ` [PATCH devicetree 1/2] dt-bindings: arm: fsl: document the LX2160A BlueBox 3 boards Rob Herring
2021-10-04 3:48 ` Shawn Guo [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=20211004034815.GC15650@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vladimir.oltean@nxp.com \
/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).