From: John Stultz <johnstul@us.ibm.com>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
Ike Pan <ike.pan@canonical.com>,
Nadav Haklai <nadavh@marvell.com>,
Ian Molton <ian.molton@codethink.co.uk>,
David Marlin <dmarlin@redhat.com>,
Yehuda Yitschak <yehuday@marvell.com>,
Jani Monoses <jani.monoses@canonical.com>,
Mike Turquette <mturquette@linaro.org>,
Tawfik Bayouk <tawfik@marvell.com>,
Dan Frazier <dann.frazier@canonical.com>,
Eran Ben-Avi <benavi@marvell.com>,
Leif Lindholm <leif.lindholm@arm.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Jason Cooper <jason@lakedaemon.net>,
Arnd Bergmann <arnd@arndb.de>, Jon Masters <jcm@redhat.com>,
devicetree-discuss@lists.ozlabs.org,
Ben Dooks <ben-linux@fluff.org>,
linux-arm-kernel@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Chris Van Hoof <vanhoof@canonical.com>,
Nicolas Pitre <nico@fluxnic.net>,
linux-k
Subject: Re: [PATCH V4 3/3] clocksource: time-armada-370-xp converted to clk framework
Date: Tue, 13 Nov 2012 10:58:54 -0800 [thread overview]
Message-ID: <50A2986E.9020202@us.ibm.com> (raw)
In-Reply-To: <1351621413-3637-4-git-send-email-gregory.clement@free-electrons.com>
On 10/30/2012 11:23 AM, Gregory CLEMENT wrote:
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
> cc: John Stultz <johnstul@us.ibm.com>
> ---
> arch/arm/boot/dts/armada-370-db.dts | 4 ----
> arch/arm/boot/dts/armada-370-xp.dtsi | 1 +
> drivers/clocksource/time-armada-370-xp.c | 11 ++++++-----
> 3 files changed, 7 insertions(+), 9 deletions(-)
This is missing the patch description. Since none of it is
code/hardware I'm familiar with, I can't really closely review whats
being done. So its much more critical that the patch have a clear
description of what its doing.
thanks
-john
next prev parent reply other threads:[~2012-11-13 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 18:23 [PATCH V4 0/3] Add clock framework for armada 370/XP Gregory CLEMENT
[not found] ` <1351621413-3637-1-git-send-email-gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2012-10-30 18:23 ` [PATCH V4 1/3] clk: mvebu: add armada-370-xp specific clocks Gregory CLEMENT
2012-10-30 18:23 ` [PATCH V4 2/3] clk: armada-370-xp: add support for clock framework Gregory CLEMENT
2012-10-30 18:23 ` [PATCH V4 3/3] clocksource: time-armada-370-xp converted to clk framework Gregory CLEMENT
2012-11-13 18:58 ` John Stultz [this message]
2012-11-10 1:42 ` [PATCH V4 0/3] Add clock framework for armada 370/XP Mike Turquette
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=50A2986E.9020202@us.ibm.com \
--to=johnstul@us.ibm.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=benavi@marvell.com \
--cc=dann.frazier@canonical.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmarlin@redhat.com \
--cc=gregory.clement@free-electrons.com \
--cc=ian.molton@codethink.co.uk \
--cc=ike.pan@canonical.com \
--cc=jani.monoses@canonical.com \
--cc=jason@lakedaemon.net \
--cc=jcm@redhat.com \
--cc=leif.lindholm@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mturquette@linaro.org \
--cc=nadavh@marvell.com \
--cc=nico@fluxnic.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=vanhoof@canonical.com \
--cc=yehuday@marvell.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 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).