From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/13] ARM: SAMSUNG: allow the configuration of KERNEL HZ in plat-samsung
Date: Fri, 3 Feb 2012 16:13:43 +0000 [thread overview]
Message-ID: <20120203161343.GN889@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <016f01ccdc95$30279500$9076bf00$%kim@samsung.com>
On Fri, Jan 27, 2012 at 10:44:20AM +0900, Kukjin Kim wrote:
>
> Cc: Russell King <rmk+kernel@arm.linux.org.uk>
> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
This patch really needs some kind of explanation. It's far from obvious
from the casual reader why moving from a fixed value of 200Hz for the
kernel tick rate to a range from 32 to 1024 would be legal.
If 100Hz was possible before, and that's the architecture default, why
was 200Hz chosen instead?
And is 99Hz and 101Hz allowable?
prev parent reply other threads:[~2012-02-03 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 1:44 [PATCH 02/13] ARM: SAMSUNG: allow the configuration of KERNEL HZ in plat-samsung Kukjin Kim
2012-01-27 2:15 ` Kukjin Kim
2012-02-03 16:13 ` Russell King - ARM Linux [this message]
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=20120203161343.GN889@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).