From: Andrew Morton <akpm@linux-foundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel@vger.kernel.org,
John Stultz <john.stultz@linaro.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] Allow CLOCK_TICK_RATE to be undefined
Date: Wed, 18 Jul 2012 15:51:41 -0700 [thread overview]
Message-ID: <20120718155141.232ae14c.akpm@linux-foundation.org> (raw)
In-Reply-To: <1342543300-23460-1-git-send-email-catalin.marinas@arm.com>
On Tue, 17 Jul 2012 17:41:40 +0100
Catalin Marinas <catalin.marinas@arm.com> wrote:
> This patch allows an architecture to not define CLOCK_TICK_RATE, in
> which case ACTHZ defaults to (HZ << 8).
No reason was given for this change.
So those people who are wondering "why don't you just define
CLOCK_TICK_RATE" are made all sad.
next prev parent reply other threads:[~2012-07-18 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 16:41 [PATCH] Allow CLOCK_TICK_RATE to be undefined Catalin Marinas
2012-07-18 22:51 ` Andrew Morton [this message]
2012-07-18 23:11 ` John Stultz
2012-07-19 9:22 ` Catalin Marinas
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=20120718155141.232ae14c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.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).