From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: can: renesas,rcar-canfd: Make interrupt-names required
Date: Tue, 3 May 2022 10:15:42 +0200 [thread overview]
Message-ID: <878rrjf2vv.fsf@hardanger.blackshift.org> (raw)
In-Reply-To: <a68e65955e0df4db60233d468f348203c2e7b940.1651512451.git.geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
On 02.05.2022 19:33:53, Geert Uytterhoeven wrote:
> The Renesas R-Car CAN FD Controller always uses two or more interrupts.
> Make the interrupt-names properties a required property, to make it
> easier to identify the individual interrupts.
>
> Update the example accordingly.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Applied to linux-can-next/testing.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-03 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 17:33 [PATCH 0/2] dt-bindings: can: renesas,rcar-canfd: Make interrupt-names required Geert Uytterhoeven
2022-05-02 17:33 ` [PATCH 1/2] arm64: dts: renesas: Add interrupt-names to CANFD nodes Geert Uytterhoeven
2022-05-02 17:33 ` [PATCH 2/2] dt-bindings: can: renesas,rcar-canfd: Make interrupt-names required Geert Uytterhoeven
2022-05-03 8:15 ` Marc Kleine-Budde [this message]
2022-05-02 18:26 ` [PATCH 0/2] " Marc Kleine-Budde
2022-05-03 7:25 ` Geert Uytterhoeven
2022-05-03 8:13 ` Marc Kleine-Budde
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=878rrjf2vv.fsf@hardanger.blackshift.org \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=wg@grandegger.com \
/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).