summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCao jin <caoj.fnst@cn.fujitsu.com>2016-04-21 16:39:15 +0300
committerJonathan Corbet <corbet@lwn.net>2016-04-28 16:13:10 +0300
commitac86db349e2df2e2d6b786cbacefa3037126f3bc (patch)
tree8b69570f4d48bc5d1c4122d37b2631b4a831959a
parent2c30322c4795bf26a74b6049bbea6267a19036a4 (diff)
downloadlinux-ac86db349e2df2e2d6b786cbacefa3037126f3bc.tar.xz
hrtimers: doc cleanup
It has: a tense correction(led->leads); a typo(unevitably->inevitably); Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/timers/hrtimers.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/timers/hrtimers.txt b/Documentation/timers/hrtimers.txt
index ce31f65e12e7..492f1affb0e5 100644
--- a/Documentation/timers/hrtimers.txt
+++ b/Documentation/timers/hrtimers.txt
@@ -28,9 +28,9 @@ several reasons why such integration is hard/impossible:
- the unpredictable [O(N)] overhead of cascading leads to delays which
necessitate a more complex handling of high resolution timers, which
- in turn decreases robustness. Such a design still led to rather large
+ in turn decreases robustness. Such a design still leads to rather large
timing inaccuracies. Cascading is a fundamental property of the timer
- wheel concept, it cannot be 'designed out' without unevitably
+ wheel concept, it cannot be 'designed out' without inevitably
degrading other portions of the timers.c code in an unacceptable way.
- the implementation of the current posix-timer subsystem on top of