devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Marty Jones <mj8263788@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: Add doc for FriendlyARM NanoPi NEO3
Date: Mon, 11 Jan 2021 14:09:14 -0600	[thread overview]
Message-ID: <20210111200914.GA2985472@robh.at.kernel.org> (raw)
In-Reply-To: <20201228141150.2ccc4f30@marty-x570>

On Mon, Dec 28, 2020 at 02:11:50PM -0500, Marty Jones wrote:
> From 4979bc740c982a15f36002fbb97979cba5d99739 Mon Sep 17 00:00:00 2001
> From: Marty Jones <mj8263788@gmail.com>
> Date: Mon, 28 Dec 2020 13:16:53 -0500
> Subject: [PATCH] dt-bindings: Add doc for FriendlyARM NanoPi NEO3

Your patch is corrupted.

> 
> Add devicetree binding documentation for the FriendlyARM NanoPi NEO3
> 
> Signed-off-by: Marty Jones <mj8263788@gmail.com>
> ---
>  Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
> index ef4544ad6f82..a0aaae08c97b 100644
> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> @@ -122,6 +122,11 @@ properties:
>                - firefly,roc-rk3399-pc-mezzanine
>            - const: rockchip,rk3399
>  
> +      - description: FriendlyElec NanoPi NEO3
> +        items:
> +          - const: friendlyarm,nanopi-neo3
> +          - const: rockchip,rk3328
> +
>        - description: FriendlyElec NanoPi R2S
>          items:
>            - const: friendlyarm,nanopi-r2s
> -- 
> 2.27.0
> 

      reply	other threads:[~2021-01-11 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 19:11 [PATCH] dt-bindings: Add doc for FriendlyARM NanoPi NEO3 Marty Jones
2021-01-11 20:09 ` 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=20210111200914.GA2985472@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mj8263788@gmail.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).