From: Rob Herring <robh@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: devicetree@vger.kernel.org, arinc.unal@arinc9.com,
tsbogend@alpha.franken.de, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org
Subject: Re: [PATCH v3] dt-bindings: interrupt-controller: migrate MIPS CPU interrupt controller text bindings to YAML
Date: Mon, 26 Sep 2022 14:13:35 -0500 [thread overview]
Message-ID: <20220926191335.GA2614072-robh@kernel.org> (raw)
In-Reply-To: <20220921072405.610739-1-sergio.paracuellos@gmail.com>
On Wed, 21 Sep 2022 09:24:05 +0200, Sergio Paracuellos wrote:
> MIPS CPU interrupt controller bindings used text format, so migrate them
> to YAML.
>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> Changes in v3:
> - Remmove 'bindings' keyword from title.
> - Put 'compatible' the first also in node sample.
>
> Changes in v2:
> - Address review comment from Krzysztof:
> - Rebase onto last kernel version.
> - Add Thomas Bogendoerfer as maintainer since this is arch stuff.
> - Change compatible to go first as property and required.
> - Change sample node name to be generic. Use 'interrupt-controller'.
>
> .../mti,cpu-interrupt-controller.yaml | 46 ++++++++++++++++++
> .../devicetree/bindings/mips/cpu_irq.txt | 47 -------------------
> 2 files changed, 46 insertions(+), 47 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/mti,cpu-interrupt-controller.yaml
> delete mode 100644 Documentation/devicetree/bindings/mips/cpu_irq.txt
>
Applied, thanks!
prev parent reply other threads:[~2022-09-26 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 7:24 [PATCH v3] dt-bindings: interrupt-controller: migrate MIPS CPU interrupt controller text bindings to YAML Sergio Paracuellos
2022-09-21 7:46 ` Krzysztof Kozlowski
2022-09-26 19:13 ` 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=20220926191335.GA2614072-robh@kernel.org \
--to=robh@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.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;
as well as URLs for NNTP newsgroup(s).