From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] clocksource: tegra20: use the device_node pointer passed to init
Date: Thu, 07 Feb 2013 12:39:40 -0700 [thread overview]
Message-ID: <511402FC.50807@wwwdotorg.org> (raw)
In-Reply-To: <1360264144-20714-5-git-send-email-robherring2@gmail.com>
On 02/07/2013 12:09 PM, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
>
> We've already matched the node, so use the node pointer passed in. The rtc
> init was intermingled with the timer init, so split this out to a separate
> init function.
The series,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
Patches 1,4:
Tested-by: Stephen Warren <swarren@nvidia.com>
One thing I wonder re: patch 4 - I know someone (I think Hiroshi, now
CC'd) planned to refactor drivers/clocksource/tegra20_timer.c to enhance
it for Tegra114. I'd like to check with him that the refactoring in this
patch won't impede that at all.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Rob Herring <robherring2@gmail.com>, Hiroshi Doyu <hdoyu@nvidia.com>
Cc: arm@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <rob.herring@calxeda.com>,
John Stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH 4/4] clocksource: tegra20: use the device_node pointer passed to init
Date: Thu, 07 Feb 2013 12:39:40 -0700 [thread overview]
Message-ID: <511402FC.50807@wwwdotorg.org> (raw)
In-Reply-To: <1360264144-20714-5-git-send-email-robherring2@gmail.com>
On 02/07/2013 12:09 PM, Rob Herring wrote:
> From: Rob Herring <rob.herring@calxeda.com>
>
> We've already matched the node, so use the node pointer passed in. The rtc
> init was intermingled with the timer init, so split this out to a separate
> init function.
The series,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
Patches 1,4:
Tested-by: Stephen Warren <swarren@nvidia.com>
One thing I wonder re: patch 4 - I know someone (I think Hiroshi, now
CC'd) planned to refactor drivers/clocksource/tegra20_timer.c to enhance
it for Tegra114. I'd like to check with him that the refactoring in this
patch won't impede that at all.
next prev parent reply other threads:[~2013-02-07 19:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 19:09 [PATCH 0/4] Improve CLKSRC_OF matching Rob Herring
2013-02-07 19:09 ` Rob Herring
2013-02-07 19:09 ` [PATCH 1/4] clocksource: pass DT node pointer to init functions Rob Herring
2013-02-07 19:09 ` Rob Herring
2013-02-13 16:21 ` Michal Simek
2013-02-13 16:21 ` Michal Simek
2013-02-13 16:33 ` Rob Herring
2013-02-13 16:33 ` Rob Herring
2013-02-13 17:33 ` Michal Simek
2013-02-13 17:33 ` Michal Simek
2013-02-14 1:30 ` Rob Herring
2013-02-14 1:30 ` Rob Herring
2013-02-14 6:45 ` Michal Simek
2013-02-14 6:45 ` Michal Simek
2013-02-14 14:22 ` Rob Herring
2013-02-14 14:22 ` Rob Herring
2013-02-07 19:09 ` [PATCH 2/4] clocksource: bcm2835: use the device_node pointer passed to init Rob Herring
2013-02-07 19:09 ` Rob Herring
2013-02-09 3:47 ` Stephen Warren
2013-02-09 3:47 ` Stephen Warren
2013-02-07 19:09 ` [PATCH 3/4] clocksource: vt8500: " Rob Herring
2013-02-07 19:09 ` Rob Herring
2013-02-07 19:09 ` [PATCH 4/4] clocksource: tegra20: " Rob Herring
2013-02-07 19:09 ` Rob Herring
2013-02-07 19:39 ` Stephen Warren [this message]
2013-02-07 19:39 ` Stephen Warren
2013-02-07 20:05 ` Hiroshi Doyu
2013-02-07 20:05 ` Hiroshi Doyu
2013-02-07 22:44 ` [PATCH 0/4] Improve CLKSRC_OF matching Arnd Bergmann
2013-02-07 22:44 ` Arnd Bergmann
2013-02-07 23:36 ` Rob Herring
2013-02-07 23:36 ` Rob Herring
2013-02-07 23:45 ` Arnd Bergmann
2013-02-07 23:45 ` Arnd Bergmann
2013-02-08 4:51 ` Tony Prisk
2013-02-08 4:51 ` Tony Prisk
2013-02-08 13:07 ` Rob Herring
2013-02-08 13:07 ` Rob Herring
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=511402FC.50807@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.