From: Pavel Pisa <pisa@cmp.felk.cvut.cz>
To: "Marc Kleine-Budde" <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Ondrej Ille <ondrej.ille@gmail.com>
Subject: Re: [PATCH can-next] dt-binding: can: ctucanfd: include common CAN controller bindings
Date: Wed, 4 May 2022 09:37:53 +0200 [thread overview]
Message-ID: <202205040937.53137.pisa@cmp.felk.cvut.cz> (raw)
In-Reply-To: <20220504062342.52529-1-mkl@pengutronix.de>
Hello Marc,
thanks for update
On Wednesday 04 of May 2022 08:23:42 Marc Kleine-Budde wrote:
> Since commit
>
> | 1f9234401ce0 ("dt-bindings: can: add can-controller.yaml")
>
> there is a common CAN controller binding. Add this to the ctucanfd
> binding.
>
> Cc: Pavel Pisa <pisa@cmp.felk.cvut.cz>
> Cc: Ondrej Ille <ondrej.ille@gmail.com>
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
if my reaction is expected then you can add my
Acked-by: Pavel Pisa <pisa@cmp.felk.cvut.cz>
> ---
> Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml
> b/Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml index
> fb34d971dcb3..4635cb96fc64 100644
> --- a/Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml
> +++ b/Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml
> @@ -25,6 +25,9 @@ maintainers:
> - Ondrej Ille <ondrej.ille@gmail.com>
> - Martin Jerabek <martin.jerabek01@gmail.com>
>
> +allOf:
> + - $ref: can-controller.yaml#
> +
> properties:
> compatible:
> oneOf:
next prev parent reply other threads:[~2022-05-04 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 6:23 [PATCH can-next] dt-binding: can: ctucanfd: include common CAN controller bindings Marc Kleine-Budde
2022-05-04 7:37 ` Pavel Pisa [this message]
2022-05-04 7:55 ` Marc Kleine-Budde
2022-05-04 15:28 ` Rob Herring
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=202205040937.53137.pisa@cmp.felk.cvut.cz \
--to=pisa@cmp.felk.cvut.cz \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=ondrej.ille@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).