From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: dts: renesas: r8a77965: Add CAN FD controller node
Date: Mon, 19 Nov 2018 00:10:53 +0100 [thread overview]
Message-ID: <20181118231053.GC2553@kunai> (raw)
In-Reply-To: <20181118173327.4704-2-marek.vasut+renesas@gmail.com>
On Sun, Nov 18, 2018 at 06:33:27PM +0100, Marek Vasut wrote:
> From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>
> This patch adds CAN FD controller nodes for the R8A77965 SoC.
>
> Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> Cc: Marc Kleine-Budde <mkl@pengutronix.de>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Simon Horman <horms+renesas@verge.net.au>
> Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Cc: linux-renesas-soc at vger.kernel.org
> Cc: linux-arm-kernel at lists.infradead.org
Why seperate patches for CAN and CANFD here while they are merged for
r8a77990 into one patch?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20181119/4c3d1f32/attachment.sig>
next prev parent reply other threads:[~2018-11-18 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 17:33 [PATCH 1/2] arm64: dts: renesas: r8a77965: Add CAN controller nodes Marek Vasut
2018-11-18 17:33 ` [PATCH 2/2] arm64: dts: renesas: r8a77965: Add CAN FD controller node Marek Vasut
2018-11-18 23:10 ` Wolfram Sang [this message]
2018-11-18 23:29 ` Marek Vasut
2018-11-19 10:44 ` Simon Horman
2018-11-20 23:33 ` Marek Vasut
2018-11-18 23:02 ` [PATCH 1/2] arm64: dts: renesas: r8a77965: Add CAN controller nodes Wolfram Sang
2018-11-18 23:46 ` Marek Vasut
2018-11-19 9:00 ` Geert Uytterhoeven
2018-11-20 23:30 ` Marek Vasut
2018-11-21 7:37 ` Geert Uytterhoeven
2018-12-05 16:50 ` Marek Vasut
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=20181118231053.GC2553@kunai \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox