linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: Re: [PATCH v2 5/5] arm64: dts: renesas: r8a774c0: Add TMU device nodes
Date: Tue, 5 Feb 2019 16:06:12 +0100	[thread overview]
Message-ID: <20190205150612.7ac5xns67gkzi3ii@verge.net.au> (raw)
In-Reply-To: <1549272007-33471-6-git-send-email-biju.das@bp.renesas.com>

On Mon, Feb 04, 2019 at 09:20:07AM +0000, Biju Das wrote:
> This patch adds TMU{0|1|2|3|4} device nodes for r8a774c0 SoC.
> 
> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> V1-->V2 No change

Thanks, applied for v5.1

  reply	other threads:[~2019-02-05 15:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04  9:20 [PATCH v2 0/5] Add CMT/TMU support for RZ/G2E Biju Das
2019-02-04  9:20 ` [PATCH v2 1/5] dt-bindings: timer: renesas, cmt: Document r8a774c0 CMT support Biju Das
2019-02-05 14:56   ` Simon Horman
2019-02-04  9:20 ` [PATCH v2 2/5] arm64: dts: renesas: r8a774c0: Add CMT device nodes Biju Das
2019-02-05 15:01   ` Simon Horman
2019-02-04  9:20 ` [PATCH v2 3/5] clk: renesas: r8a774c0: Add TMU clock Biju Das
2019-02-05  8:22   ` Geert Uytterhoeven
2019-02-04  9:20 ` [PATCH v2 4/5] dt-bindings: timer: renesas: tmu: Document r8a774c0 bindings Biju Das
2019-02-05 15:04   ` Simon Horman
2019-02-04  9:20 ` [PATCH v2 5/5] arm64: dts: renesas: r8a774c0: Add TMU device nodes Biju Das
2019-02-05 15:06   ` Simon Horman [this message]
2019-02-12 10:03 ` [PATCH v2 0/5] Add CMT/TMU support for RZ/G2E Daniel Lezcano
2019-02-12 10:17   ` Biju Das
2019-02-13  8:44     ` Daniel Lezcano
2019-02-14 12:46       ` Simon Horman

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=20190205150612.7ac5xns67gkzi3ii@verge.net.au \
    --to=horms@verge.net.au \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).