kernel: fix typos and some coding style in comments
Subsystems (2)
PATCH v2 1/1 kernel: fix typos and some coding style in comments
fix lenght to length
Signed-off-by Weitao Hou <[email protected]>
---
Changes in v2:
- fix space before tab warnings
--- kernel/sysctl.c | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-)
kernel/sysctl.c +9 -9
@@ -187,17 +187,17 @@ extern int no_unaligned_warning;* enum sysctl_writes_mode - supported sysctl write modes * * @SYSCTL_WRITES_LEGACY: each write syscall must fully contain the sysctl value -* to be written, and multiple writes on the same sysctl file descriptor -* will rewrite the sysctl value, regardless of file position. No warning -* is issued when the initial position is not 0. +* to be written, and multiple writes on the same sysctl file descriptor +* will rewrite the sysctl value, regardless of file position. No warning +* is issued when the initial position is not 0. * @SYSCTL_WRITES_WARN: same as above but warn when the initial file position is -* not 0. +* not 0. * @SYSCTL_WRITES_STRICT: writes to numeric sysctl entries must always be at -* file position 0 and the value must be fully contained in the buffer -* sent to the write syscall. If dealing with strings respect the file -* position, but restrict this to the max length of the buffer, anything -* passed the max lenght will be ignored. Multiple writes will append -* to the buffer. +* file position 0 and the value must be fully contained in the buffer +* sent to the write syscall. If dealing with strings respect the file +* position, but restrict this to the max length of the buffer, anything +* passed the max length will be ignored. Multiple writes will append +* to the buffer. * * These write modes control how current file position affects the behavior of * updating sysctl values through the proc interface on each write.
Signature · 1 line
2.18.0
Quoted 1 line · Weitao Hou
fix lenght to length
What about the other instances of this misspelling? (See "git grep lenght").
-Kees
Quoted 43 lines
Signed-off-by Weitao Hou <[email protected]>---
Changes in v2:
- fix space before tab warnings--- kernel/sysctl.c | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-)kernel/sysctl.c +9
-9@@ -187,17 +187,17 @@ extern int no_unaligned_warning;* enum sysctl_writes_mode - supported sysctl write modes * * @SYSCTL_WRITES_LEGACY: each write syscall must fully contain the sysctl value -* to be written, and multiple writes on the same sysctl file descriptor -* will rewrite the sysctl value, regardless of file position. No warning -* is issued when the initial position is not 0. +* to be written, and multiple writes on the same sysctl file descriptor +* will rewrite the sysctl value, regardless of file position. No warning +* is issued when the initial position is not 0. * @SYSCTL_WRITES_WARN: same as above but warn when the initial file position is -* not 0. +* not 0. * @SYSCTL_WRITES_STRICT: writes to numeric sysctl entries must always be at -* file position 0 and the value must be fully contained in the buffer -* sent to the write syscall. If dealing with strings respect the file -* position, but restrict this to the max length of the buffer, anything -* passed the max lenght will be ignored. Multiple writes will append -* to the buffer. +* file position 0 and the value must be fully contained in the buffer +* sent to the write syscall. If dealing with strings respect the file +* position, but restrict this to the max length of the buffer, anything +* passed the max length will be ignored. Multiple writes will append +* to the buffer. * * These write modes control how current file position affects the behavior of * updating sysctl values through the proc interface on each write. Signature · 1 line
2.18.0
Signature · 1 line
Kees Cook