From: patchwork-bot+netdevbpf@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, wsa@kernel.org,
yoshihiro.shimoda.uh@renesas.com, wg@grandegger.com,
mkl@pengutronix.de, kuba@kernel.org, mailhol.vincent@wanadoo.fr,
socketcan@hartkopp.net, geert@linux-m68k.org,
kieran.bingham@ideasonboard.com, horms@verge.net.au
Subject: Re: [PATCH v4 0/4] can: rcar_canfd: Add support for V3U flavor
Date: Fri, 11 Mar 2022 04:20:16 +0000 [thread overview]
Message-ID: <164697241634.8307.12005930852651825961.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220309162609.3726306-1-uli+renesas@fpond.eu>
Hello:
This series was applied to netdev/net-next.git (master)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Wed, 9 Mar 2022 17:26:05 +0100 you wrote:
> Hi!
>
> This adds CANFD support for V3U (R8A779A0) SoCs. The V3U's IP supports up
> to eight channels and has some other minor differences to the Gen3 variety:
>
> - changes to some register offsets and layouts
> - absence of "classic CAN" registers, both modes are handled through the
> CANFD register set
>
> [...]
Here is the summary with links:
- [v4,1/4] can: rcar_canfd: Add support for r8a779a0 SoC
https://git.kernel.org/netdev/net-next/c/45721c406dcf
- [v4,2/4] arm64: dts: renesas: r8a779a0: Add CANFD device node
(no matching commit)
- [v4,3/4] arm64: dts: renesas: r8a779a0-falcon: enable CANFD 0 and 1
(no matching commit)
- [v4,4/4] dt-bindings: can: renesas,rcar-canfd: Document r8a779a0 support
https://git.kernel.org/netdev/net-next/c/d6254d52d70d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-03-11 4:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 16:26 [PATCH v4 0/4] can: rcar_canfd: Add support for V3U flavor Ulrich Hecht
2022-03-09 16:26 ` [PATCH v4 1/4] can: rcar_canfd: Add support for r8a779a0 SoC Ulrich Hecht
2022-03-10 1:14 ` Vincent MAILHOL
2022-03-09 16:26 ` [PATCH v4 2/4] arm64: dts: renesas: r8a779a0: Add CANFD device node Ulrich Hecht
2022-03-11 17:04 ` Geert Uytterhoeven
2022-03-09 16:26 ` [PATCH v4 3/4] arm64: dts: renesas: r8a779a0-falcon: enable CANFD 0 and 1 Ulrich Hecht
2022-03-11 17:04 ` Geert Uytterhoeven
2022-03-14 8:04 ` Geert Uytterhoeven
2022-03-09 16:26 ` [PATCH v4 4/4] dt-bindings: can: renesas,rcar-canfd: Document r8a779a0 support Ulrich Hecht
2022-03-10 8:25 ` [PATCH v4 0/4] can: rcar_canfd: Add support for V3U flavor Marc Kleine-Budde
2022-03-10 8:32 ` Ulrich Hecht
2022-03-10 8:45 ` Geert Uytterhoeven
2022-03-10 8:50 ` Marc Kleine-Budde
2022-03-11 4:20 ` patchwork-bot+netdevbpf [this message]
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=164697241634.8307.12005930852651825961.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kieran.bingham@ideasonboard.com \
--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=wsa@kernel.org \
--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 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.