From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Simon Horman <horms+renesas@verge.net.au>,
linux-sh@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] clocksource: sh_mtu2: Drop incorrect SoC family name
Date: Sun, 26 Oct 2014 15:14:19 +0200 [thread overview]
Message-ID: <2748392.6fMSe2cx9z@avalon> (raw)
In-Reply-To: <1414150178-4986-1-git-send-email-geert+renesas@glider.be>
Hi Geert,
Thank you for the patch.
On Friday 24 October 2014 13:29:38 Geert Uytterhoeven wrote:
> The TPU2 hardware block is found in many Renesas SH and ARM SoCs, but
s/TPU2/MTU2/
With this fixed,
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> not in R-Car.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> v2:
> - Drop family name instead of changing it to RZ.
> ---
> Documentation/devicetree/bindings/timer/renesas,mtu2.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> b/Documentation/devicetree/bindings/timer/renesas,mtu2.txt index
> d9a8d5af1a21270f..ba0a34d97eb80261 100644
> --- a/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> +++ b/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> @@ -1,4 +1,4 @@
> -* Renesas R-Car Multi-Function Timer Pulse Unit 2 (MTU2)
> +* Renesas Multi-Function Timer Pulse Unit 2 (MTU2)
>
> The MTU2 is a multi-purpose, multi-channel timer/counter with configurable
> clock inputs and programmable compare match.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-10-26 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 11:29 [PATCH v2] clocksource: sh_mtu2: Drop incorrect SoC family name Geert Uytterhoeven
2014-10-26 13:14 ` Laurent Pinchart [this message]
2014-10-27 0:26 ` 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=2748392.6fMSe2cx9z@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.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).