From: Rob Herring <robh@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Linus Walleij <linus.walleij@linaro.org>, devicetree@vger.kernel.org
Subject: Re: [PATCH v3] dt-bindings: interrupt-controller: Convert ARM VIC to json-schema
Date: Thu, 24 Jun 2021 13:42:54 -0600 [thread overview]
Message-ID: <20210624194254.GA1869153@robh.at.kernel.org> (raw)
In-Reply-To: <20210617205317.3060163-1-sudeep.holla@arm.com>
On Thu, 17 Jun 2021 21:53:17 +0100, Sudeep Holla wrote:
> Convert the ARM VIC binding document to DT schema format using
> json-schema.
>
> Cc: Rob Herring <robh@kernel.org>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> .../bindings/interrupt-controller/arm,vic.txt | 41 ----------
> .../interrupt-controller/arm,vic.yaml | 81 +++++++++++++++++++
> 2 files changed, 81 insertions(+), 41 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/arm,vic.txt
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/arm,vic.yaml
>
> v2[2]->v3:
> - Dropped unnecessary maxItems and description fields as suggested
> - Used enum instead of oneOf
> - Reverted back to GPL-2.0
>
> v1[1]->v2[2]:
> - Added arm,versatile-vic to the list of compatibles as suggested
> by Linus W and added his review tag
> - Updated the SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>
> [1] https://lore.kernel.org/r/20210610135717.2782793-1-sudeep.holla@arm.com/
> [2] https://lore.kernel.org/r/20210611111033.2818949-1-sudeep.holla@arm.com/
>
Applied, thanks!
prev parent reply other threads:[~2021-06-24 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 20:53 [PATCH v3] dt-bindings: interrupt-controller: Convert ARM VIC to json-schema Sudeep Holla
2021-06-24 19:42 ` 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=20210624194254.GA1869153@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=sudeep.holla@arm.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).