lkml.org 
[lkml]   [2016]   [Apr]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH] hrtimers: doc cleanup
Date
It has:
a tense correction(led->leads);
a typo(unevitably->inevitably);
a logic error correction(unacceptable->acceptable)

Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
---
Documentation/timers/hrtimers.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/timers/hrtimers.txt b/Documentation/timers/hrtimers.txt
index ce31f65..347ad82 100644
--- a/Documentation/timers/hrtimers.txt
+++ b/Documentation/timers/hrtimers.txt
@@ -28,10 +28,10 @@ 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
- degrading other portions of the timers.c code in an unacceptable way.
+ wheel concept, it cannot be 'designed out' without inevitably
+ degrading other portions of the timers.c code in an acceptable way.

- the implementation of the current posix-timer subsystem on top of
the timer wheel has already introduced a quite complex handling of
--
2.1.0


\
 
 \ /
  Last update: 2016-04-21 11:21    [W:0.097 / U:1.292 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site