From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org,
Wolfgang Grandegger <wg@grandegger.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] DT: net: can: rcar_canfd: document R8A77980 bindings
Date: Mon, 30 Apr 2018 09:37:22 +0200 [thread overview]
Message-ID: <20180430073722.tbrd5y3bs5hpq724@verge.net.au> (raw)
In-Reply-To: <556f1f23-19bc-e7bd-47b1-f22e086e2b69@cogentembedded.com>
On Fri, Apr 27, 2018 at 09:53:33PM +0300, Sergei Shtylyov wrote:
> Document the R-Car V3H (R8A77980) SoC support in the R-Car CAN-FD bindings.
>
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> ---
> The patch is against the 'linux-can-next.git' repo plus the R8A77970 bindings
> patch posted yesterday. Although I wouldn't object if they're both merged to
> the 'linux-can.git' repo instead. :-)
>
> Documentation/devicetree/bindings/net/can/rcar_canfd.txt | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
>
> Index: linux-can-next/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
> ===================================================================
> --- linux-can-next.orig/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
> +++ linux-can-next/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
> @@ -7,6 +7,7 @@ Required properties:
> - "renesas,r8a7795-canfd" for R8A7795 (R-Car H3) compatible controller.
> - "renesas,r8a7796-canfd" for R8A7796 (R-Car M3) compatible controller.
> - "renesas,r8a77970-canfd" for R8A77970 (R-Car V3M) compatible controller.
> + - "renesas,r8a77980-canfd" for R8A77980 (R-Car V3H) compatible controller.
>
> When compatible with the generic version, nodes must list the
> SoC-specific version corresponding to the platform first, followed by the
>
next prev parent reply other threads:[~2018-04-30 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 18:53 [PATCH] DT: net: can: rcar_canfd: document R8A77980 bindings Sergei Shtylyov
2018-04-30 7:37 ` Simon Horman [this message]
2018-04-30 8:18 ` Marc Kleine-Budde
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=20180430073722.tbrd5y3bs5hpq724@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=wg@grandegger.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