From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Prabhakar <prabhakar.csengg+renesas@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 3/3] arm64: dts: renesas: rzt2h-n2h-evk: Enable RTC support
Date: Mon, 24 Aug 2026 11:25:59 +0200 [thread overview]
Message-ID: <aowOJx0TMIZMyFUa@ninjato> (raw)
In-Reply-To: <20260824075936.2904336-4-prabhakar.mahadev-lad.rj@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 158 bytes --]
> + rtc0 = &rtc0;
Maybe 'rtc' instead of 'rtc0' throughout the patchset?
@Geert: do we have a rule for this? There is also only 'gic' instead of
'gic0'?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-08-24 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 7:59 [PATCH 0/3] Enable RTC support on RZ/T2H and RZ/N2H SoCs Prabhakar
2026-08-24 7:59 ` [PATCH 1/3] arm64: dts: renesas: r9a09g077: Add RTC node Prabhakar
2026-08-24 8:13 ` sashiko-bot
2026-08-25 12:22 ` Geert Uytterhoeven
2026-08-24 7:59 ` [PATCH 2/3] arm64: dts: renesas: r9a09g087: " Prabhakar
2026-08-24 8:11 ` sashiko-bot
2026-08-25 12:22 ` Geert Uytterhoeven
2026-08-24 7:59 ` [PATCH 3/3] arm64: dts: renesas: rzt2h-n2h-evk: Enable RTC support Prabhakar
2026-08-24 8:08 ` sashiko-bot
2026-08-31 10:14 ` Geert Uytterhoeven
2026-08-24 9:25 ` Wolfram Sang [this message]
2026-08-24 12:32 ` Geert Uytterhoeven
2026-08-24 9:30 ` Wolfram Sang
2026-08-25 12:23 ` Geert Uytterhoeven
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=aowOJx0TMIZMyFUa@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.csengg+renesas@gmail.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@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.