From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] One more sched_clock() patch
Date: Mon, 27 Feb 2012 09:44:42 +0100 [thread overview]
Message-ID: <322c288d3ad6aecc8014e0a3582c8527@localhost> (raw)
Russell,
Could you please pull from my sched_clock-for-rmk branch again?
It contains a single additional patch. courtesy of Stephen Boyd, that
contains support for sched_clock() on msm. The rest of the branch is
unchanged.
Thanks,
M.
The following changes since commit
6905a65879b51d326396e63dfea40861a30bc17f:
ARM: Make the sched_clock framework mandatory (2012-02-03 11:34:27
+0000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
sched_clock-for-rmk
Stephen Boyd (1):
msm: timer: Support sched_clock()
arch/arm/mach-msm/timer.c | 12 ++++++++++--
1 files changed, 10 insertions(+), 2 deletions(-)
--
Fast, cheap, reliable. Pick two.
next reply other threads:[~2012-02-27 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 8:44 Marc Zyngier [this message]
2012-03-07 21:32 ` [GIT PULL] One more sched_clock() patch Stephen Boyd
2012-03-07 21:38 ` Russell King - ARM Linux
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=322c288d3ad6aecc8014e0a3582c8527@localhost \
--to=marc.zyngier@arm.com \
--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).