lib/test: Fix spelling mistakes
Subsystems (6)
v2 cover lib/test: Fix spelling mistakes
v1 --> v2:
Add "found by codespell" to the commit message.
Zhen Lei (1):
lib/test: Fix spelling mistakes
lib/test_bitops.c | 2 +- lib/test_bpf.c | 2 +- lib/test_kasan.c | 2 +- lib/test_kmod.c | 6 +++--- lib/test_scanf.c | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-)
Signature · 1 line
2.25.1
PATCH v2 1/1 lib/test: Fix spelling mistakes
Fix some spelling mistakes in comments found by "codespell":
thats ==> that's
unitialized ==> uninitialized
panicing ==> panicking
sucess ==> success
possitive ==> positive
intepreted ==> interpreted
Signed-off-by Zhen Lei <[email protected]>
--- lib/test_bitops.c | 2 +- lib/test_bpf.c | 2 +- lib/test_kasan.c | 2 +- lib/test_kmod.c | 6 +++--- lib/test_scanf.c | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-)
lib/test_bitops.c +1 -1
@@ -15,7 +15,7 @@* get_count_order/long */ -/* use an enum because thats the most common BITMAP usage */ +/* use an enum because that's the most common BITMAP usage */ enum bitops_fun {BITOPS_4 =4 ,BITOPS_7 =7 ,
lib/test_bpf.c +1 -1
@@ -1095,7 +1095,7 @@ static struct bpf_test tests[] = { { "RET_A", .u.insns = { -/* check that unitialized X and A contain zeros */ +/* check that uninitialized X and A contain zeros */ BPF_STMT (BPF_MISC |BPF_TXA ,0 ),BPF_STMT (BPF_RET |BPF_A ,0 ) },
lib/test_kasan.c +1 -1
@@ -656,7 +656,7 @@ static void kasan_global_oob(struct kunit *test) {/* * Deliberate out-of-bounds access. To prevent CONFIG_UBSAN_LOCAL_BOUNDS -* from failing here and panicing the kernel, access the array via a +* from failing here and panicking the kernel, access the array via a * volatile pointer, which will prevent the compiler from being able to * determine the array bounds. *
lib/test_kmod.c +3 -3
@@ -286,7 +286,7 @@ static int tally_work_test(struct kmod_test_device_info *info)* If this ran it means *all* tasks were created fine and we * are now just collecting results. * -* Only propagate errors, do not override with a subsequent sucess case. +* Only propagate errors, do not override with a subsequent success case. */ static void tally_up_work (struct kmod_test_device *test_dev) {
@@ -543,7 +543,7 @@ static int trigger_config_run(struct kmod_test_device *test_dev)* wrong with the setup of the test. If the test setup went fine * then userspace must just check the result of config->test_result. * One issue with relying on the return from a call in the kernel -* is if the kernel returns a possitive value using this trigger +* is if the kernel returns a positive value using this trigger * will not return the value to userspace, it would be lost. * * By not relying on capturing the return value of tests we are using
@@ -585,7 +585,7 @@ trigger_config_store(struct device *dev,* Note: any return > 0 will be treated as success * and the error value will not be available to userspace. * Do not rely on trying to send to userspace a test value -* return value as possitive return errors will be lost. +* return value as positive return errors will be lost. */ if (WARN_ON (ret >0 ))return -EINVAL ;
lib/test_scanf.c +1 -1
@@ -600,7 +600,7 @@ static void __init numbers_prefix_overflow(void)/* * 0x prefix in a field of width 2 using %i conversion: first field * converts to 0. Next field scan starts at the character after "0x", -* which will convert if can be intepreted as decimal but will fail +* which will convert if can be interpreted as decimal but will fail * if it contains any hex digits (since no 0x prefix). */ test_number_prefix(long long, "0x67", "%2lli%lli", 0, 67, 2, check_ll);
Signature · 1 line
2.25.1
Quoted 9 lines · Zhen Lei
Fix some spelling mistakes in comments found by "codespell":
thats ==> that's
unitialized ==> uninitialized
panicing ==> panicking
sucess ==> success
possitive ==> positive
intepreted ==> interpretedSigned-off-by Zhen Lei <[email protected]>
Ack for lib/test_bpf.c change:
Acked-by Yonghong Song <[email protected]>