diff options
author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-10-03 16:55:17 -0400 |
---|---|---|
committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 16:55:17 -0400 |
commit | 53cb47268e6b38180d9f253527135e1c69c5d310 (patch) | |
tree | b264d89e3d21f0365fc4df0f32f5070bb4c6e91a /Documentation/hrtimers.txt | |
parent | d6bc8ac9e13e466e844313b590fbc49f7f1abdea (diff) |
Fix typos in Documentation/: 'S'
This patch fixes typos in various Documentation txts. The patch addresses
some words starting with the letter 'S'.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Alan Cox <alan@redhat.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/hrtimers.txt')
-rw-r--r-- | Documentation/hrtimers.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/hrtimers.txt b/Documentation/hrtimers.txt index 1fbad1a7b809..ce31f65e12e7 100644 --- a/Documentation/hrtimers.txt +++ b/Documentation/hrtimers.txt | |||
@@ -58,7 +58,7 @@ several reasons why such integration is hard/impossible: | |||
58 | The primary users of precision timers are user-space applications that | 58 | The primary users of precision timers are user-space applications that |
59 | utilize nanosleep, posix-timers and itimer interfaces. Also, in-kernel | 59 | utilize nanosleep, posix-timers and itimer interfaces. Also, in-kernel |
60 | users like drivers and subsystems which require precise timed events | 60 | users like drivers and subsystems which require precise timed events |
61 | (e.g. multimedia) can benefit from the availability of a seperate | 61 | (e.g. multimedia) can benefit from the availability of a separate |
62 | high-resolution timer subsystem as well. | 62 | high-resolution timer subsystem as well. |
63 | 63 | ||
64 | While this subsystem does not offer high-resolution clock sources just | 64 | While this subsystem does not offer high-resolution clock sources just |
@@ -68,7 +68,7 @@ The increasing demand for realtime and multimedia applications along | |||
68 | with other potential users for precise timers gives another reason to | 68 | with other potential users for precise timers gives another reason to |
69 | separate the "timeout" and "precise timer" subsystems. | 69 | separate the "timeout" and "precise timer" subsystems. |
70 | 70 | ||
71 | Another potential benefit is that such a seperation allows even more | 71 | Another potential benefit is that such a separation allows even more |
72 | special-purpose optimization of the existing timer wheel for the low | 72 | special-purpose optimization of the existing timer wheel for the low |
73 | resolution and low precision use cases - once the precision-sensitive | 73 | resolution and low precision use cases - once the precision-sensitive |
74 | APIs are separated from the timer wheel and are migrated over to | 74 | APIs are separated from the timer wheel and are migrated over to |
@@ -96,8 +96,8 @@ file systems. The rbtree is solely used for time sorted ordering, while | |||
96 | a separate list is used to give the expiry code fast access to the | 96 | a separate list is used to give the expiry code fast access to the |
97 | queued timers, without having to walk the rbtree. | 97 | queued timers, without having to walk the rbtree. |
98 | 98 | ||
99 | (This seperate list is also useful for later when we'll introduce | 99 | (This separate list is also useful for later when we'll introduce |
100 | high-resolution clocks, where we need seperate pending and expired | 100 | high-resolution clocks, where we need separate pending and expired |
101 | queues while keeping the time-order intact.) | 101 | queues while keeping the time-order intact.) |
102 | 102 | ||
103 | Time-ordered enqueueing is not purely for the purposes of | 103 | Time-ordered enqueueing is not purely for the purposes of |