From: Pavel Machek <pavel@denx.de>
To: Claudiu <claudiu.beznea@tuxon.dev>
Cc: nobuhiro1.iwamatsu@toshiba.co.jp, cip-dev@lists.cip-project.org
Subject: Re: [PATCH 6.12.y-cip 0/7] RZ/G3S: Backport SCIF support
Date: Tue, 3 Jun 2025 11:40:25 +0200 [thread overview]
Message-ID: <aD7DCYegyFHbp0eu@duo.ucw.cz> (raw)
In-Reply-To: <20250603092005.3917850-1-claudiu.beznea.uj@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
Hi!
> Series backports the Renesas RZ/G3S SCIF support to v6.12.y CIP.
Looks good to me. I can apply it provided it passes testing and there
are no other comments.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-06-03 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 9:19 [PATCH 6.12.y-cip 0/7] RZ/G3S: Backport SCIF support Claudiu
2025-06-03 9:19 ` [PATCH 6.12.y-cip 1/7] clk: renesas: r9a08g045: Add clock, reset and power domain for the remaining SCIFs Claudiu
2025-06-03 9:20 ` [PATCH 6.12.y-cip 2/7] serial: sh-sci: Update the suspend/resume support Claudiu
2025-06-03 9:20 ` [PATCH 6.12.y-cip 3/7] serial: sh-sci: Save and restore more registers Claudiu
2025-06-03 9:20 ` [PATCH 6.12.y-cip 4/7] arm64: dts: renesas: r9a08g045: Add the remaining SCIF interfaces Claudiu
2025-06-03 9:20 ` [PATCH 6.12.y-cip 5/7] arm64: dts: renesas: rzg3s-smarc-switches: Add a header to describe different switches Claudiu
2025-06-03 9:20 ` [PATCH 6.12.y-cip 6/7] arm64: dts: renesas: rzg3s-smarc: Enable SCIF3 Claudiu
2025-06-03 9:20 ` [PATCH 6.12.y-cip 7/7] arm64: dts: renesas: r9a08g045s33-smarc-pmod: Add overlay for SCIF1 Claudiu
2025-06-03 9:40 ` Pavel Machek [this message]
2025-06-04 6:17 ` [PATCH 6.12.y-cip 0/7] RZ/G3S: Backport SCIF support nobuhiro1.iwamatsu
2025-06-04 18:12 ` Pavel Machek
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=aD7DCYegyFHbp0eu@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
/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.