From: Kevin Hilman <khilman@mvista.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH 0/4] 32k timer reorg and sched_clock cleanup
Date: Mon, 12 Nov 2007 15:24:01 -0800 [thread overview]
Message-ID: <20071112232401.723638265@mvista.com> (raw)
[ resend of previous series, with more sched_clock cleanup ]
Here's a short series of patches to reorganize and consolidate the 32k
timer code and the implementation of sched_clock(). In particular,
conslidate the usage of DM timers, move the OMAP1 specifics into
mach-omap1, and have only one sched_clock().
Kevin
--
next reply other threads:[~2007-11-12 23:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 23:24 Kevin Hilman [this message]
2007-11-12 23:24 ` [PATCH 1/4] ARM: OMAP: re-organize duplicated 32k-timer code Kevin Hilman
2007-11-12 23:24 ` [PATCH 2/4] ARM: OMAP: Move 32k-based sched_clock() to common code Kevin Hilman
2007-11-12 23:24 ` [PATCH 3/4] ARM: OMAP: Remove MPU-timer based sched_clock() Kevin Hilman
2007-11-23 19:18 ` Tony Lindgren
2007-11-23 20:26 ` Tony Lindgren
2007-11-26 15:59 ` Kevin Hilman
2007-11-26 18:40 ` Tony Lindgren
2007-11-26 19:30 ` Kevin Hilman
2007-11-26 20:12 ` Tony Lindgren
2007-11-12 23:24 ` [PATCH 4/4] ARM: OMAP: Move timer32k to mach-omap1 Kevin Hilman
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=20071112232401.723638265@mvista.com \
--to=khilman@mvista.com \
--cc=linux-omap-open-source@linux.omap.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 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.