devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Corentin Labbe <clabbe@baylibre.com>,
	devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: arm: Convert Gemini boards to YAML
Date: Thu, 29 Jul 2021 15:25:13 -0600	[thread overview]
Message-ID: <YQMcuZH/hDkvCSD/@robh.at.kernel.org> (raw)
In-Reply-To: <20210723152356.1874088-1-linus.walleij@linaro.org>

On Fri, 23 Jul 2021 17:23:56 +0200, Linus Walleij wrote:
> This removes the old plaintext Gemini binding and replace it
> with a YAML schema, adding some new boards in the process.
> While we are at it, add the missing vendors to the vendor
> prefix file.
> 
> Drop the overly deliberate description of subnodes and the big
> example from the old document. Keep the elaborate description.
> 
> I noticed that "wiliboard" is not a real vendor, the vendor
> is named "wiligear" so deprecated this and replaced with the
> proper vendor.
> 
> Cc: Corentin Labbe <clabbe@baylibre.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Rob: maybe it's best that you apply this directly to the bindings
> tree so the vendors file is kept in check.
> ---
>  .../devicetree/bindings/arm/gemini.txt        | 108 ------------------
>  .../devicetree/bindings/arm/gemini.yaml       |  95 +++++++++++++++
>  .../devicetree/bindings/vendor-prefixes.yaml  |  10 ++
>  3 files changed, 105 insertions(+), 108 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/arm/gemini.txt
>  create mode 100644 Documentation/devicetree/bindings/arm/gemini.yaml
> 

Applied, thanks!

      reply	other threads:[~2021-07-29 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 15:23 [PATCH] dt-bindings: arm: Convert Gemini boards to YAML Linus Walleij
2021-07-29 21:25 ` 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=YQMcuZH/hDkvCSD/@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=clabbe@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh+dt@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).