From: Pavel Machek <pavel@nabladev.com>
To: Ovidiu Panait <ovidiu.panait.rb@renesas.com>
Cc: cip-dev@lists.cip-project.org, pavel@nabladev.com,
nobuhiro.iwamatsu.x90@mail.toshiba
Subject: Re: [PATCH 6.12.y-cip 0/5] Add RZ/V2N Interrupt Controller Unit (ICU) support
Date: Wed, 11 Mar 2026 11:34:20 +0100 [thread overview]
Message-ID: <abFFLOUfBwQWKZpc@duo.ucw.cz> (raw)
In-Reply-To: <20260310160050.40977-1-ovidiu.panait.rb@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
Hi!
> This series adds Interrupt Controller Unit (ICU) support for the
> Renesas RZ/V2N SoC.
>
> Patches were cherry-picked from mainline kernel.
>
> Note: This series depends on:
> https://lore.kernel.org/cip-dev/20260305153725.19821-1-ovidiu.panait.rb@renesas.com/
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-03-11 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 16:00 [PATCH 6.12.y-cip 0/5] Add RZ/V2N Interrupt Controller Unit (ICU) support Ovidiu Panait
2026-03-10 16:00 ` [PATCH 6.12.y-cip 1/5] dt-bindings: interrupt-controller: renesas,rzv2h-icu: Document RZ/V2N SoC Ovidiu Panait
2026-03-10 16:00 ` [PATCH 6.12.y-cip 2/5] clk: renesas: r9a09g056: Add entries for ICU Ovidiu Panait
2026-03-10 16:00 ` [PATCH 6.12.y-cip 3/5] irqchip/renesas-rzv2h: Add support for RZ/V2N SoC Ovidiu Panait
2026-03-10 16:00 ` [PATCH 6.12.y-cip 4/5] arm64: dts: renesas: r9a09g056: Add ICU node Ovidiu Panait
2026-03-10 16:00 ` [PATCH 6.12.y-cip 5/5] arm64: dts: renesas: r9a09g056n48-rzv2n-evk: Add NMI wakeup button support Ovidiu Panait
2026-03-11 10:34 ` Pavel Machek [this message]
2026-03-12 3:34 ` [cip-dev] [PATCH 6.12.y-cip 0/5] Add RZ/V2N Interrupt Controller Unit (ICU) 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=abFFLOUfBwQWKZpc@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=ovidiu.panait.rb@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