From: Cao Van Dong <cv-dong@jinso.co.jp>
To: Simon Horman <horms@verge.net.au>
Cc: broonie@kernel.org, geert+renesas@glider.be,
devicetree@vger.kernel.org, yoshihiro.shimoda.uh@renesas.com,
kuninori.morimoto.gx@renesas.com,
linux-renesas-soc@vger.kernel.org, h-inayoshi@jinso.co.jp,
nv-dung@jinso.co.jp, na-hoan@jinso.co.jp
Subject: Re: [PATCH 1/4] arm64: dts: renesas: r8a7795: Add CMT device nodes
Date: Fri, 5 Apr 2019 18:02:30 +0900 [thread overview]
Message-ID: <d666b4d4-4b78-201f-c7a1-f41bd5c1cf71@jinso.co.jp> (raw)
In-Reply-To: <20190405081716.s74zbrd47ychcevw@verge.net.au>
Dear Simon-san,
On 2019/04/05 17:17, Simon Horman wrote:
> On Fri, Apr 05, 2019 at 02:44:06PM +0900, Cao Van Dong wrote:
>> This patch adds CMT{0|1|2|3} device nodes for r8a7795 SoC.
>>
>> Tested-by: Cao Van Dong <cv-dong@jinso.co.jp>
>> Signed-off-by: Cao Van Dong <cv-dong@jinso.co.jp>
> Thanks,
>
> This looks fine to me but I will wait to see if there are other reviews
> before applying.
>
> Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
Thanks you for review!
> I am, however, curious to know how you tested this.
>
> Likewise for patches 2/4 and 3/4.
Always thanks for your curious!
After booting, I checked the existence of the device and the device
interrupt.
Thanks you,
Dong
next prev parent reply other threads:[~2019-04-05 9:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 5:44 [PATCH 0/4] Add CMT support for R-Car H3/M3-N/E3 Cao Van Dong
2019-04-05 5:44 ` [PATCH 1/4] arm64: dts: renesas: r8a7795: Add CMT device nodes Cao Van Dong
2019-04-05 8:17 ` Simon Horman
2019-04-05 9:02 ` Cao Van Dong [this message]
2019-04-10 9:22 ` Simon Horman
2019-04-30 14:24 ` Geert Uytterhoeven
2019-04-05 5:44 ` [PATCH 2/4] arm64: dts: renesas: r8a77965: " Cao Van Dong
2019-04-30 14:25 ` Geert Uytterhoeven
2019-04-05 5:44 ` [PATCH 3/4] arm64: dts: renesas: r8a77990: " Cao Van Dong
2019-04-30 14:26 ` Geert Uytterhoeven
2019-04-05 5:44 ` [PATCH 4/4] dt-bindings: timer: renesas, cmt: Document r8a779{5|65|90} CMT support Cao Van Dong
2019-04-05 8:03 ` Simon Horman
2019-04-10 9:23 ` Simon Horman
2019-04-29 17:27 ` Rob Herring
2019-04-30 14:26 ` Geert Uytterhoeven
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=d666b4d4-4b78-201f-c7a1-f41bd5c1cf71@jinso.co.jp \
--to=cv-dong@jinso.co.jp \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=h-inayoshi@jinso.co.jp \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=na-hoan@jinso.co.jp \
--cc=nv-dung@jinso.co.jp \
--cc=yoshihiro.shimoda.uh@renesas.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.