mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
synced 2024-12-29 17:22:07 +00:00
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 Link: https://lkml.kernel.org/r/20210607133036.12525-2-thunder.leizhen@huawei.com Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com> Acked-by: Yonghong Song <yhs@fb.com> [test_bfp.c] Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
a931dd33d3
commit
53b0fe36ab
@ -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,
|
||||
|
@ -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)
|
||||
},
|
||||
|
@ -651,7 +651,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.
|
||||
*
|
||||
|
@ -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;
|
||||
|
@ -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);
|
||||
|
Loading…
Reference in New Issue
Block a user