From: Rob Herring <robh@kernel.org>
To: Dharma Balasubiramani <dharma.b@microchip.com>
Cc: claudiu.beznea@tuxon.dev, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, alexandre.belloni@bootlin.com,
Conor Dooley <conor.dooley@microchip.com>,
Nicolas.Ferre@microchip.com, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4] dt-bindings: interrupt-controller: Convert Atmel AIC to json-schema
Date: Mon, 4 Mar 2024 07:38:52 -0600 [thread overview]
Message-ID: <170955953165.116756.5262999318809520557.robh@kernel.org> (raw)
In-Reply-To: <20240222090738.41628-1-dharma.b@microchip.com>
On Thu, 22 Feb 2024 14:37:38 +0530, Dharma Balasubiramani wrote:
> Convert the Atmel AIC binding document to DT schema format using
> json-schema.
>
> Signed-off-by: Dharma Balasubiramani <dharma.b@microchip.com>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> Changelog
> v3 -> v4
> - Move the allOf after "atmel,external-irqs" as it handles its restriction.
> v2 -> v3
> - Add constraints to the "atmel,external-irqs" property.
> - Move 'reg' before 'interrupt-controller' in the example.
> v1 -> v2
> - Drop the '|' as there is no formatting to preserve.
> - Remove unnecessary marketing statement from description.
> - Drop the description for interrupts and reg, it's obvious.
> - Put reg after compatible.
> - Drop comment in example.
> - Drop the example of device that is wired to an AIC as it's(dma) binding is
> not yet available.
> ---
> .../interrupt-controller/atmel,aic.txt | 43 ---------
> .../interrupt-controller/atmel,aic.yaml | 89 +++++++++++++++++++
> 2 files changed, 89 insertions(+), 43 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/atmel,aic.txt
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/atmel,aic.yaml
>
Applied, thanks!
prev parent reply other threads:[~2024-03-04 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 9:07 Dharma Balasubiramani
2024-03-04 13:38 ` 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=170955953165.116756.5262999318809520557.robh@kernel.org \
--to=robh@kernel.org \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dharma.b@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®