From: "Rob Herring (Arm)" <robh@kernel.org>
To: "J. Neuschäfer" <j.ne@posteo.net>
Cc: Conor Dooley <conor+dt@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, Crystal Wood <oss@buserror.net>,
linux-kernel@vger.kernel.org, Naveen N Rao <naveen@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: interrupt-controller: Convert fsl,mpic-msi to YAML
Date: Mon, 30 Jun 2025 16:36:28 -0500 [thread overview]
Message-ID: <175131938693.3399448.343722096560779428.robh@kernel.org> (raw)
In-Reply-To: <20250611-msipic-yaml-v2-1-f2e174c48802@posteo.net>
On Wed, 11 Jun 2025 11:42:09 +0200, J. Neuschäfer wrote:
> As part of a larger effort to bring various PowerPC-related bindings
> into the YAML world, this patch converts msi-pic.txt to YAML and moves
> it into the bindings/interrupt-controller/ directory. The conversion may
> necessarily be a bit hard to read because the binding is quite verbose.
>
> Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
> ---
> Changes in v2:
> - Rebase on v6.16-rc1
> - Address Conor Dooley's review comments:
> - Add multiline marker (|) to preserve formatting
> - Split 'reg' list in second example
> - Rewrite version dependent information as an if/else schema
>
> Link to v1: https://lore.kernel.org/r/20250403-msipic-yaml-v1-1-f4248475714f@posteo.net
> ---
> ---
> .../interrupt-controller/fsl,mpic-msi.yaml | 161 +++++++++++++++++++++
> .../devicetree/bindings/powerpc/fsl/msi-pic.txt | 111 --------------
> 2 files changed, 161 insertions(+), 111 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2025-06-30 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 9:42 [PATCH v2] dt-bindings: interrupt-controller: Convert fsl,mpic-msi to YAML J. Neuschäfer via B4 Relay
2025-06-25 20:12 ` Rob Herring
2025-06-29 1:47 ` J. Neuschäfer
2025-06-30 21:36 ` Rob Herring (Arm) [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=175131938693.3399448.343722096560779428.robh@kernel.org \
--to=robh@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.ne@posteo.net \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=oss@buserror.net \
--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;
as well as URLs for NNTP newsgroup(s).