diff options
| author | Eric Engestrom <eric@engestrom.ch> | 2016-04-25 08:37:00 +0200 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2016-04-28 15:26:41 +0200 |
| commit | 86cbbe24b4120aa4813c8519eb2b1506147fe0a0 (patch) | |
| tree | 08e110e98766fd2c394504c4c241697053c66319 | |
| parent | Documentation: pps: fix spelling mistake (diff) | |
| download | linux-86cbbe24b4120aa4813c8519eb2b1506147fe0a0.tar.xz linux-86cbbe24b4120aa4813c8519eb2b1506147fe0a0.zip | |
Documentation: robust-futexes: fix spelling mistakes
Signed-off-by: Eric Engestrom <eric@engestrom.ch>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
| -rw-r--r-- | Documentation/robust-futexes.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/robust-futexes.txt b/Documentation/robust-futexes.txt index af6fce23e484..61c22d608759 100644 --- a/Documentation/robust-futexes.txt +++ b/Documentation/robust-futexes.txt @@ -126,9 +126,9 @@ vma based method: - no VM changes are needed - 'struct address_space' is left alone. - - no registration of individual locks is needed: robust mutexes dont + - no registration of individual locks is needed: robust mutexes don't need any extra per-lock syscalls. Robust mutexes thus become a very - lightweight primitive - so they dont force the application designer + lightweight primitive - so they don't force the application designer to do a hard choice between performance and robustness - robust mutexes are just as fast. @@ -202,7 +202,7 @@ and the remaining bits are for the TID. Testing, architecture support ----------------------------- -i've tested the new syscalls on x86 and x86_64, and have made sure the +I've tested the new syscalls on x86 and x86_64, and have made sure the parsing of the userspace list is robust [ ;-) ] even if the list is deliberately corrupted. |