From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: use clockevents_config_and_register() where possible
Date: Tue, 27 Nov 2012 09:04:36 +1300 [thread overview]
Message-ID: <1353960276.2327.1.camel@gitbox> (raw)
In-Reply-To: <1353936857-15313-1-git-send-email-shawn.guo@linaro.org>
On Mon, 2012-11-26 at 21:34 +0800, Shawn Guo wrote:
> The clockevent core is able to figure out the best mult and shift,
> calculate min_delta_ns and max_delta_ns, with the necessary info passed
> into clockevents_config_and_register(). Use this combined configure
> and register function where possible to make the codes less error prone
> and gain some positive diff stat.
Acked-by: Tony Prisk <linux@prisktech.co.nz>
next prev parent reply other threads:[~2012-11-26 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 13:34 [PATCH] ARM: use clockevents_config_and_register() where possible Shawn Guo
2012-11-26 14:44 ` Roland Stigge
2012-11-26 14:57 ` viresh kumar
2012-11-26 20:04 ` Tony Prisk [this message]
2012-11-26 21:55 ` Stephen Warren
2012-11-27 1:18 ` Tony Lindgren
2012-11-27 1:19 ` Anton Vorontsov
2012-11-27 1:55 ` Eric Miao
2012-11-27 8:58 ` Arnd Bergmann
2012-11-28 2:37 ` Barry Song
2012-11-28 5:07 ` Kukjin Kim
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=1353960276.2327.1.camel@gitbox \
--to=linux@prisktech.co.nz \
--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 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).