From: sashiko-bot@kernel.org
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>
Cc: wsa+renesas@sang-engineering.com, devicetree@vger.kernel.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
conor+dt@kernel.org, linux-rtc@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 3/4] dt-bindings: rtc: rzn1: add R-Car Gen5 support
Date: Wed, 16 Sep 2026 10:31:28 +0000 [thread overview]
Message-ID: <20260916103129.3A1331F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260916102520.24288-4-wsa+renesas@sang-engineering.com>
> In general, the RTC on R-Car Gen5 is identical to RZ/T2H. X5H is an
> exception, though, because interrupts are not wired. X5H2 will have them
> wired again.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260916102520.24288-1-wsa+renesas@sang-engineering.com?part=3
next prev parent reply other threads:[~2026-09-16 10:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 10:25 [PATCH v2 0/4] rtc: rzn1: cleanups, R-Car Gen5 enablement Wolfram Sang
2026-09-16 10:25 ` [PATCH v2 1/4] dt-bindings: rtc: rzn1: drop unneeded 'start-year' from example Wolfram Sang
2026-09-16 10:27 ` sashiko-bot
2026-09-16 13:23 ` Geert Uytterhoeven
2026-09-16 10:25 ` [PATCH v2 2/4] dt-bindings: rtc: rzn1: add SoC names next to their IDs Wolfram Sang
2026-09-16 10:27 ` sashiko-bot
2026-09-16 13:24 ` Geert Uytterhoeven
2026-09-16 10:25 ` [PATCH v2 3/4] dt-bindings: rtc: rzn1: add R-Car Gen5 support Wolfram Sang
2026-09-16 10:31 ` sashiko-bot [this message]
2026-09-16 12:13 ` Lad, Prabhakar
2026-09-16 13:25 ` Geert Uytterhoeven
2026-09-24 21:51 ` Rob Herring (Arm)
2026-09-16 10:25 ` [PATCH v2 4/4] " Wolfram Sang
2026-09-16 10:31 ` sashiko-bot
2026-09-16 12:19 ` Lad, Prabhakar
2026-09-16 13:33 ` Geert Uytterhoeven
2026-09-16 21:36 ` Wolfram Sang
2026-09-16 11:45 ` [PATCH v2 0/4] rtc: rzn1: cleanups, R-Car Gen5 enablement Wolfram Sang
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=20260916103129.3A1331F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.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 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.