From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Simon Horman <horms@verge.net.au>
Cc: Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 5/6] dt-bindings: timer: renesas: tmu: Document r8a774a1 bindings
Date: Mon, 2 Sep 2019 10:42:23 +0200 [thread overview]
Message-ID: <244ca7ac-54d1-d07d-762f-e832b0e2a267@linaro.org> (raw)
In-Reply-To: <CAMuHMdVuj1w_bQVPySpspk4OJPN1cNSF-JW6XKExTEdZbtALgw@mail.gmail.com>
On 02/09/2019 10:39, Geert Uytterhoeven wrote:
> On Mon, Sep 2, 2019 at 10:32 AM Simon Horman <horms@verge.net.au> wrote:
>> On Fri, Aug 30, 2019 at 10:37:54AM +0000, Fabrizio Castro wrote:
>>> This patch has been reviewed by Geert, Simon, and Rob, so I think it's ok to apply.
>>> Is anybody willing to take this patch?
>>
>> <2c> I think Geert can take this </2c>
>
> If the timer people won't take it for v5.4, I can queue it in renesas-devel
> for v5.5, in my branch for DT binding updates for subsystems that are
> less DT-centric.
Please do, thanks
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<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-09-02 8:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 13:06 [PATCH 0/6] Add USB2.0/CMT/TMU support to HiHope RZ/G2M Fabrizio Castro
2019-06-11 13:06 ` [PATCH 1/6] arm64: dts: renesas: r8a774a1: Fix USB 2.0 clocks Fabrizio Castro
2019-06-17 8:05 ` Simon Horman
2019-06-11 13:06 ` [PATCH 2/6] arm64: dts: renesas: hihope-common: Add USB 2.0 support Fabrizio Castro
2019-06-17 8:06 ` Simon Horman
2019-06-11 13:06 ` [PATCH 3/6] arm64: dts: renesas: r8a774a1: Add CMT device nodes Fabrizio Castro
2019-06-12 7:02 ` Geert Uytterhoeven
2019-06-12 12:27 ` Simon Horman
2019-06-11 13:06 ` [PATCH 5/6] dt-bindings: timer: renesas: tmu: Document r8a774a1 bindings Fabrizio Castro
2019-06-12 6:52 ` Geert Uytterhoeven
2019-06-12 12:21 ` Simon Horman
2019-07-09 2:34 ` Rob Herring
2019-08-30 10:37 ` Fabrizio Castro
2019-09-02 8:32 ` Simon Horman
2019-09-02 8:39 ` Geert Uytterhoeven
2019-09-02 8:42 ` Daniel Lezcano [this message]
2019-09-03 12:10 ` Geert Uytterhoeven
2019-06-11 13:06 ` [PATCH 6/6] arm64: dts: renesas: r8a774a1: Add TMU device nodes Fabrizio Castro
2019-06-12 6:56 ` Geert Uytterhoeven
2019-06-12 12:29 ` Simon Horman
2019-06-11 13:12 ` [PATCH 0/6] Add USB2.0/CMT/TMU support to HiHope RZ/G2M 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=244ca7ac-54d1-d07d-762f-e832b0e2a267@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=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--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).