From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Biju Das <biju.das@bp.renesas.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] Add CMT/TMU support for RZ/G2E
Date: Wed, 13 Feb 2019 09:44:18 +0100 [thread overview]
Message-ID: <ea8a581f-56ce-bea0-86d6-7688741c3fca@linaro.org> (raw)
In-Reply-To: <OSBPR01MB210392463D9EB86AE0BE8C36B8650@OSBPR01MB2103.jpnprd01.prod.outlook.com>
On 12/02/2019 11:17, Biju Das wrote:
> Hi Daniel,
>
> Thanks for the feedback.
>
>> -----Original Message-----
>> From: Daniel Lezcano <daniel.lezcano@linaro.org>
>> Sent: 12 February 2019 10:03
>> To: Biju Das <biju.das@bp.renesas.com>; Rob Herring
>> <robh+dt@kernel.org>; Mark Rutland <mark.rutland@arm.com>
>> Cc: Thomas Gleixner <tglx@linutronix.de>; devicetree@vger.kernel.org;
>> Simon Horman <horms@verge.net.au>; Geert Uytterhoeven
>> <geert+renesas@glider.be>; Chris Paterson
>> <Chris.Paterson2@renesas.com>; Fabrizio Castro
>> <fabrizio.castro@bp.renesas.com>; linux-renesas-soc@vger.kernel.org
>> Subject: Re: [PATCH v2 0/5] Add CMT/TMU support for RZ/G2E
>>
>> On 04/02/2019 10:20, Biju Das wrote:
>>> This patch series aims to add CMT/TMU timer support for RZ/G2E SoC.
>>>
>>> This patch series is tested against renesas-dev and linux-next.
>>
>> Do you want me to take the patch 1/5 and 4/5 through my tree ?
>
> Yes, please.
>
Both applied for 5.1.
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2019-02-13 8:44 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
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 [this message]
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=ea8a581f-56ce-bea0-86d6-7688741c3fca@linaro.org \
--to=daniel.lezcano@linaro.org \
--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=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).