From: Pavel Machek <pavel@nabladev.com>
To: tommaso.merciai.xr@bp.renesas.com
Cc: cip-dev@lists.cip-project.org,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
Pavel Machek <pavel@nabladev.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
tomm.merciai@gmail.com
Subject: Re: [cip-dev] [PATCH 6.12.y-cip 0/4] Add RZ/G3E DMAC support
Date: Wed, 28 Jan 2026 20:36:25 +0100 [thread overview]
Message-ID: <aXplOU/fgckpEbAT@duo.ucw.cz> (raw)
In-Reply-To: <20260128160048.1445926-1-tommaso.merciai.xr@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
Hi!
> This series adds DMAC support for the Renesas RZ/G3E SoC into linux-cip
> 6.12.y-cip kernel. Backported also commit
> e57389d5547ee24b472ac5c8f8a7dc21b063ad73 upstream on top of this series.
As with 6.1 version, this looks okay to me.
Reviewed-by: Pavel Machek <pavel@nabladev.com>
I can apply the series if it passes testing and there are no other
comments.
Best regards,
Pavel
--
In cooperation with Nabla.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-01-28 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 16:00 [PATCH 6.12.y-cip 0/4] Add RZ/G3E DMAC support Tommaso Merciai
2026-01-28 16:00 ` [PATCH 6.12.y-cip 1/4] clk: renesas: r9a09g047: Add DMAC clocks and resets Tommaso Merciai
2026-01-28 16:00 ` [PATCH 6.12.y-cip 2/4] dt-bindings: dma: rz-dmac: Document RZ/G3E family of SoCs Tommaso Merciai
2026-01-28 16:00 ` [PATCH 6.12.y-cip 3/4] arm64: dts: renesas: r9a09g047: Add DMAC nodes Tommaso Merciai
2026-01-28 16:00 ` [PATCH 6.12.y-cip 4/4] arm64: dts: renesas: r9a09g047: Move interrupt-parent to root node Tommaso Merciai
2026-01-28 19:36 ` Pavel Machek [this message]
2026-02-02 2:09 ` [cip-dev] [PATCH 6.12.y-cip 0/4] Add RZ/G3E DMAC support nobuhiro.iwamatsu.x90
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=aXplOU/fgckpEbAT@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tomm.merciai@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.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