devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
To: Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-can@vger.kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-kernel@vger.kernel.org,
	Prabhakar <prabhakar.csengg@gmail.com>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [RESEND PATCH v2 0/2] dt-bindings: can: document R8A774E1
Date: Mon,  5 Oct 2020 09:13:17 +0100	[thread overview]
Message-ID: <20201005081319.29322-1-prabhakar.mahadev-lad.rj@bp.renesas.com> (raw)

Hi All,

I am re-sending this patch set as this has been missed previously.
It is exactly same as [1].

DT maintainers have already acked the patches.

[1] https://www.spinics.net/lists/netdev/msg679244.html

Cheers,
Prabhakar

Changes for v2:
* Added R8A774E1 to the list of SoCs that can use CANFD through "clkp2".
* Added R8A774E1 to the list of SoCs that can use the CANFD clock

Lad Prabhakar (2):
  dt-bindings: can: rcar_canfd: Document r8a774e1 support
  dt-bindings: can: rcar_can: Document r8a774e1 support

 Documentation/devicetree/bindings/net/can/rcar_can.txt   | 5 +++--
 Documentation/devicetree/bindings/net/can/rcar_canfd.txt | 5 +++--
 2 files changed, 6 insertions(+), 4 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-10-05  8:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05  8:13 Lad Prabhakar [this message]
2020-10-05  8:13 ` [RESEND PATCH v2 1/2] dt-bindings: can: rcar_canfd: Document r8a774e1 support Lad Prabhakar
2020-10-05  8:13 ` [RESEND PATCH v2 2/2] dt-bindings: can: rcar_can: " Lad Prabhakar
2020-10-06 19:20 ` [RESEND PATCH v2 0/2] dt-bindings: can: document R8A774E1 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=20201005081319.29322-1-prabhakar.mahadev-lad.rj@bp.renesas.com \
    --to=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=prabhakar.csengg@gmail.com \
    --cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).