From: Krzysztof Kozlowski <krzk@kernel.org>
To: Atharv Dubey <atharvd440@gmail.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Jassi Brar <jaswinder.singh@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] mailbox: dt-bindings: mailbox: Convert to DT-SCHEMA
Date: Sun, 22 Mar 2026 10:00:01 +0100 [thread overview]
Message-ID: <dc7a2041-50a4-482e-9930-566bb3fd1e72@kernel.org> (raw)
In-Reply-To: <20260322-mailbox-v1-1-c6251f18187c@gmail.com>
On 21/03/2026 22:20, Atharv Dubey wrote:
> Convert the Generic Mailbox Controller and Client
> binding from text format to DT schema format.
>
> Signed-off-by: Atharv Dubey <atharvd440@gmail.com>
> ---
> .../devicetree/bindings/mailbox/mailbox.txt | 60 -----------------
> .../devicetree/bindings/mailbox/mailbox.yaml | 78 ++++++++++++++++++++++
> 2 files changed, 78 insertions(+), 60 deletions(-)
Isn't the binding in general already converted in dtschema?
...
> +
> +maintainers:
> + - Jassi Brar <jaswinder.singh@linaro.org>
> +
> +description:
> + Generic binding to provide a way for Mailbox controller drivers to
> + assign appropriate mailbox channel to client drivers.
> +
> +select: false
What is the point in such case? This patch makes little sense. If there
is useful text, it should be moved to dtschema. Unless it is already
there. And only after getting acks for relicensing.
But I cannot find anything useful here, so this file should stay only
for the purpose of providing context.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-22 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 21:20 [PATCH] mailbox: dt-bindings: mailbox: Convert to DT-SCHEMA Atharv Dubey
2026-03-21 22:33 ` Rob Herring (Arm)
2026-03-22 6:05 ` kernel test robot
2026-03-22 9:00 ` Krzysztof Kozlowski [this message]
2026-03-23 13:35 ` Rob Herring
2026-03-23 14:28 ` Atharv Dubey
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=dc7a2041-50a4-482e-9930-566bb3fd1e72@kernel.org \
--to=krzk@kernel.org \
--cc=atharvd440@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=jaswinder.singh@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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