From: Wolfram Sang <wsa@kernel.org>
To: Ulrich Hecht <uli+renesas@fpond.eu>
Cc: linux-renesas-soc@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, linux-can@vger.kernel.org,
prabhakar.mahadev-lad.rj@bp.renesas.com,
biju.das.jz@bp.renesas.com, yoshihiro.shimoda.uh@renesas.com,
wg@grandegger.com, mkl@pengutronix.de, kuba@kernel.org,
mailhol.vincent@wanadoo.fr, socketcan@hartkopp.net
Subject: Re: [PATCH 1/3] can: rcar_canfd: Add support for r8a779a0 SoC
Date: Fri, 24 Sep 2021 18:34:51 +0200 [thread overview]
Message-ID: <YU3+K5WQkBC2YBBy@ninjato> (raw)
In-Reply-To: <20210924153113.10046-2-uli+renesas@fpond.eu>
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
> 1 file changed, 152 insertions(+), 75 deletions(-)
Nice work, Ulrich. Compared to the BSP patch which has "422
insertions(+), 128 deletions(-)", this is a really good improvement.
Did you test it on D3 to ensure there is no regression? Or are the
additions in a way that they don't affect older versions?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-24 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 15:31 [PATCH 0/3] can: rcar_canfd: Add support for V3U flavor Ulrich Hecht
2021-09-24 15:31 ` [PATCH 1/3] can: rcar_canfd: Add support for r8a779a0 SoC Ulrich Hecht
2021-09-24 16:34 ` Wolfram Sang [this message]
2021-09-28 8:47 ` Ulrich Hecht
2021-10-05 13:06 ` Geert Uytterhoeven
2021-10-18 12:50 ` Marc Kleine-Budde
2022-01-11 16:21 ` Ulrich Hecht
2021-09-24 15:31 ` [PATCH 2/3] dt-bindings: can: renesas,rcar-canfd: Document r8a779a0 support Ulrich Hecht
2021-10-05 13:15 ` Geert Uytterhoeven
2021-09-24 15:31 ` [PATCH 3/3] arm64: dts: r8a779a0: Add CANFD device node Ulrich Hecht
2021-10-05 13:20 ` Geert Uytterhoeven
2022-01-11 16:21 ` Ulrich Hecht
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=YU3+K5WQkBC2YBBy@ninjato \
--to=wsa@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=socketcan@hartkopp.net \
--cc=uli+renesas@fpond.eu \
--cc=wg@grandegger.com \
--cc=yoshihiro.shimoda.uh@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