diff options
| author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-10-03 22:55:17 +0200 |
|---|---|---|
| committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 22:55:17 +0200 |
| 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: The primary users of precision timers are user-space applications that utilize nanosleep, posix-timers and itimer interfaces. Also, in-kernel users like drivers and subsystems which require precise timed events -(e.g. multimedia) can benefit from the availability of a seperate +(e.g. multimedia) can benefit from the availability of a separate high-resolution timer subsystem as well. While this subsystem does not offer high-resolution clock sources just @@ -68,7 +68,7 @@ The increasing demand for realtime and multimedia applications along with other potential users for precise timers gives another reason to separate the "timeout" and "precise timer" subsystems. -Another potential benefit is that such a seperation allows even more +Another potential benefit is that such a separation allows even more special-purpose optimization of the existing timer wheel for the low resolution and low precision use cases - once the precision-sensitive 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 a separate list is used to give the expiry code fast access to the queued timers, without having to walk the rbtree. -(This seperate list is also useful for later when we'll introduce -high-resolution clocks, where we need seperate pending and expired +(This separate list is also useful for later when we'll introduce +high-resolution clocks, where we need separate pending and expired queues while keeping the time-order intact.) Time-ordered enqueueing is not purely for the purposes of |