diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2020-09-13 19:30:55 +0200 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2020-09-14 09:55:45 +0200 |
| commit | fab7609913c9787bdb79602ff716f5e0d1598c98 (patch) | |
| tree | 7bd1cebde179e383cbbf5868e5b664c7d0f7e88f /docs/pseudo_syscalls.md | |
| parent | 3f1d02b23f99beaf2bf3b06c11642e56578b12ee (diff) | |
tools/check-whitespace.sh: check for trailing whitespaces
File types that we don't format automatically can end up
with such basic untidiness as trailing whitespaces.
Check for these. Remove all existing precedents.
Diffstat (limited to 'docs/pseudo_syscalls.md')
| -rw-r--r-- | docs/pseudo_syscalls.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/pseudo_syscalls.md b/docs/pseudo_syscalls.md index 82c2bfeb8..5247dd6b3 100644 --- a/docs/pseudo_syscalls.md +++ b/docs/pseudo_syscalls.md @@ -4,7 +4,7 @@ Besides regular system calls, a [syscall description](syscall_descriptions.md) file can also contain pseudo-syscalls. These are C functions defined in the executor. When a test program uses a pseudo-syscall, the executor -will generate the pseudo-syscall function code in the resulting C program. +will generate the pseudo-syscall function code in the resulting C program. This allows a test program to have specific code blocks to perform certain actions, they may also be used as more test-friendly wrappers |