All of lore.kernel.org
 help / color / mirror / Atom feed
From: Biju Das <biju.das.jz@bp.renesas.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Biju Das <biju.das@bp.renesas.com>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: RE: [PATCH v3 0/3] Add RZ/N1 CAN support
Date: Mon, 5 Sep 2022 16:13:09 +0000	[thread overview]
Message-ID: <OS0PR01MB59227189DB7DC3721B097B9F867F9@OS0PR01MB5922.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20220905160758.ieo673gvaejjjfuk@pengutronix.de>

Hi Marc,

> Subject: Re: [PATCH v3 0/3] Add RZ/N1 CAN support
> 
> On 30.08.2022 17:45:15, Biju Das wrote:
> > This patch series supports CAN{0,1} populated on RZ/N1D-DB board.
> >
> > v2->v3:
> >  * Documented power-domains support.
> >  * Dropped clock-names property from CAN nodes.
> >  * Added power-domains property to the CAN nodes.
> > v1->v2:
> >  * Added RZ/N1 specific compatible string.
> >  * Added clock-names property.
> >
> > This patch series depend upon [1]
> > [1] https://lore.kernel.org/linux-renesas-
> soc/20220819084532.ywtziogd7ycuozxx@pengutronix.de/
> >
> > Biju Das (3):
> >   dt-bindings: can: nxp,sja1000: Document RZ/N1 power-domains support
> >   ARM: dts: r9a06g032: Add CAN{0,1} nodes
> >   ARM: dts: r9a06g032-rzn1d400-db: Enable CAN{0,1}
> 
> Who will take this series (once it's ready)?

I guess, normally bindings by respective maintainer(ie, by you) and 
Renesas SoC/board dtsi/dts by Geert. Already SoC dtsi is
queued for 6.1[1]. So I guess binding can be applied to respective subsystem
tree.

[1] https://patchwork.kernel.org/project/linux-renesas-soc/patch/20220830164518.1381632-3-biju.das.jz@bp.renesas.com/

Cheers,
Biju



  reply	other threads:[~2022-09-05 16:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 16:45 [PATCH v3 0/3] Add RZ/N1 CAN support Biju Das
2022-08-30 16:45 ` [PATCH v3 1/3] dt-bindings: can: nxp,sja1000: Document RZ/N1 power-domains support Biju Das
2022-08-30 17:31   ` Krzysztof Kozlowski
2022-08-30 17:47     ` Biju Das
2022-08-30 19:03       ` Krzysztof Kozlowski
2022-09-01 10:25         ` Geert Uytterhoeven
2022-09-01 10:22   ` Geert Uytterhoeven
2022-08-30 16:45 ` [PATCH v3 2/3] ARM: dts: r9a06g032: Add CAN{0,1} nodes Biju Das
2022-09-01 12:22   ` Geert Uytterhoeven
2022-08-30 16:45 ` [PATCH v3 3/3] ARM: dts: r9a06g032-rzn1d400-db: Enable CAN{0,1} Biju Das
2022-09-01 12:45   ` Geert Uytterhoeven
2022-09-01 13:15     ` Biju Das
2022-09-01 13:57       ` Biju Das
2022-09-01 17:06       ` Geert Uytterhoeven
2022-09-05 16:07 ` [PATCH v3 0/3] Add RZ/N1 CAN support Marc Kleine-Budde
2022-09-05 16:13   ` Biju Das [this message]
2022-09-05 20:01     ` 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=OS0PR01MB59227189DB7DC3721B097B9F867F9@OS0PR01MB5922.jpnprd01.prod.outlook.com \
    --to=biju.das.jz@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mkl@pengutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.