From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
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 <netdev@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 0/2] dt-bindings: can: renesas,rcar-canfd: Make interrupt-names required
Date: Tue, 3 May 2022 09:25:45 +0200 [thread overview]
Message-ID: <CAMuHMdU2RfBUO7SVJ8N2dUVqzvgptLX61UJY5Wdiyobj=rQgJw@mail.gmail.com> (raw)
In-Reply-To: <20220502182635.2ntwjifykmyzbjgx@pengutronix.de>
Hi Marc,
On Mon, May 2, 2022 at 8:27 PM Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> On 02.05.2022 19:33:51, Geert Uytterhoeven wrote:
> > The Renesas R-Car CAN FD Controller always uses two or more interrupts.
> > Hence it makes sense to make the interrupt-names property a required
> > property, to make it easier to identify the individual interrupts, and
> > validate the mapping.
> >
> > - The first patch updates the various R-Car Gen3 and RZ/G2 DTS files
> > to add interrupt-names properties, and is intended for the
> > renesas-devel tree,
> > - The second patch updates the CAN-FD DT bindings to mark the
> > interrupt-names property required, and is intended for the DT or net
> > tree.
> >
> > Thanks!
>
> LGTM. Who takes this series?
I'll take the first patch.
The second patch is up to you and the DT maintainers.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2022-05-03 7:26 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
2022-05-02 18:26 ` [PATCH 0/2] " Marc Kleine-Budde
2022-05-03 7:25 ` Geert Uytterhoeven [this message]
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='CAMuHMdU2RfBUO7SVJ8N2dUVqzvgptLX61UJY5Wdiyobj=rQgJw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--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=mkl@pengutronix.de \
--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).