From: buytenh@wantstofly.org (Lennert Buytenhek)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC, PATCH 0/5] unify definition of CLOCK_TICK_RATE across different platforms
Date: Wed, 20 Oct 2010 06:51:10 +0200 [thread overview]
Message-ID: <20101020045110.GW12979@mail.wantstofly.org> (raw)
One of the things preventing building an ARM multiplatform kernel
image is the fact that CLOCK_TICK_RATE (and as a consequence, LATCH)
is defined differently for each ARM platform.
The patches in this series:
- pull the per-platform CLOCK_TICK_RATE defines from <mach/timex.h>
into arch/arm/mach-foo/ (on those platforms that use the
CLOCK_TICK_RATE define and/or the LATCH define in their platform
support code);
- define CLOCK_TICK_RATE as a platform-independent value in <asm/timex.h>;
- get rid of all <mach/timex.h> include files.
Comments welcome!
next reply other threads:[~2010-10-20 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 4:51 Lennert Buytenhek [this message]
2010-10-20 6:01 ` [RFC, PATCH 0/5] unify definition of CLOCK_TICK_RATE across different platforms Eric Miao
2010-10-20 7:00 ` Linus Walleij
2010-10-20 20:30 ` 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=20101020045110.GW12979@mail.wantstofly.org \
--to=buytenh@wantstofly.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 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).