From: Rob Herring <robh@kernel.org>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
"David S. Miller" <davem@davemloft.net>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: can: rcar_canfd: Document r8a774a1 support
Date: Mon, 18 Feb 2019 14:33:57 -0600 [thread overview]
Message-ID: <20190218203357.GA19340@bogus> (raw)
In-Reply-To: <1547736856-16539-4-git-send-email-fabrizio.castro@bp.renesas.com>
On Thu, 17 Jan 2019 14:54:16 +0000, Fabrizio Castro wrote:
> Document support for rcar_canfd on R8A774A1 SoC devices.
>
> Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> Reviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>
> ---
> This patch depends on:
> https://patchwork.kernel.org/patch/10766781/
>
> Documentation/devicetree/bindings/net/can/rcar_canfd.txt | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
"David S. Miller" <davem@davemloft.net>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: can: rcar_canfd: Document r8a774a1 support
Date: Mon, 18 Feb 2019 14:33:57 -0600 [thread overview]
Message-ID: <20190218203357.GA19340@bogus> (raw)
In-Reply-To: <1547736856-16539-4-git-send-email-fabrizio.castro@bp.renesas.com>
On Thu, 17 Jan 2019 14:54:16 +0000, Fabrizio Castro wrote:
> Document support for rcar_canfd on R8A774A1 SoC devices.
>
> Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> Reviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>
> ---
> This patch depends on:
> https://patchwork.kernel.org/patch/10766781/
>
> Documentation/devicetree/bindings/net/can/rcar_canfd.txt | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-02-18 20:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 14:54 [PATCH 0/3] Correct CAN clocks definition Fabrizio Castro
2019-01-17 14:54 ` [PATCH 1/3] clk: renesas: r8a774a1: Add missing CANFD clock Fabrizio Castro
2019-01-18 12:14 ` Simon Horman
2019-01-21 13:00 ` Geert Uytterhoeven
2019-01-17 14:54 ` [PATCH 2/3] arm64: dts: renesas: r8a774a1: Add clkp2 clock to CAN nodes Fabrizio Castro
2019-01-18 12:13 ` Simon Horman
2019-01-23 9:51 ` Simon Horman
2019-01-23 11:38 ` Simon Horman
2019-01-23 12:00 ` Fabrizio Castro
2019-01-23 12:07 ` Geert Uytterhoeven
2019-01-23 12:07 ` Geert Uytterhoeven
2019-01-23 12:18 ` Fabrizio Castro
2019-01-23 12:18 ` Fabrizio Castro
2019-01-24 10:01 ` Simon Horman
2019-01-24 10:01 ` Simon Horman
2019-01-25 11:33 ` Fabrizio Castro
2019-01-25 11:33 ` Fabrizio Castro
2019-01-28 13:01 ` Simon Horman
2019-01-28 13:01 ` Simon Horman
2019-01-28 14:49 ` Fabrizio Castro
2019-01-28 14:49 ` Fabrizio Castro
2019-03-19 11:22 ` Fabrizio Castro
2019-03-19 11:22 ` Fabrizio Castro
2019-03-19 11:55 ` Simon Horman
2019-03-19 11:55 ` Simon Horman
2019-01-17 14:54 ` [PATCH 3/3] dt-bindings: can: rcar_canfd: Document r8a774a1 support Fabrizio Castro
2019-01-18 12:13 ` Simon Horman
2019-02-18 20:33 ` Rob Herring [this message]
2019-02-18 20:33 ` Rob Herring
2019-03-01 12:06 ` Fabrizio Castro
2019-03-01 12:06 ` Fabrizio Castro
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=20190218203357.GA19340@bogus \
--to=robh@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-can@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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 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.