From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-sh@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clocksource: sh_mtu2: Correct SoC family name
Date: Fri, 24 Oct 2014 11:15:16 +0900 [thread overview]
Message-ID: <20141024021513.GD7537@verge.net.au> (raw)
In-Reply-To: <1593823.SBtdMLb0Ra@avalon>
On Wed, Oct 22, 2014 at 06:00:19PM +0300, Laurent Pinchart wrote:
> Hi Geert,
>
> Thank you for the patch.
>
> On Wednesday 22 October 2014 11:26:18 Geert Uytterhoeven wrote:
> > r7s72100 is a member of the RZ family, not of the R-Car family
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Acked-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
My understanding is that mtu2 is an IP block that has been around
inside Renesas for quite some time and has a history of use
on the SH architecture as well as its more recent use on the r7s72100.
So perhaps "Renesas Multi-Function Timer Pulse Unit 2 (MTU2)"
would be (slightly) better.
> > ---
> > 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..55484a77a6ae54d0 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 RZ 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-10-24 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 9:26 [PATCH] clocksource: sh_mtu2: Correct SoC family name Geert Uytterhoeven
2014-10-22 15:00 ` Laurent Pinchart
2014-10-24 2:15 ` Simon Horman [this message]
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=20141024021513.GD7537@verge.net.au \
--to=horms@verge.net.au \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart@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).