Skip to contentSkip to conversation

KVM: selftests: Fix spelling mistake "probabalistic" -> "probabilistic"

PATCH Applied Colin Ian King 3 participants 7 messages Dec 1, 2022 – Dec 2, 2022

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 KVM: selftests: Fix spelling mistake "probabalistic" -> "probabilistic"

There is a spelling mistake in some help text. Fix it.

---
 tools/testing/selftests/kvm/dirty_log_perf_test.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/kvm/dirty_log_perf_test.c +1 -1
index c33e89012ae6..e9d6d1aecf89 100644
@@ -398,7 +398,7 @@ static void help(char *name)
 	printf(" -x: Split the memory region into this number of memslots.\n"
 	       "     (default: 1)\n");
 	printf(" -w: specify the percentage of pages which should be written to\n"
-	       "     as an integer from 0-100 inclusive. This is probabalistic,\n"
+	       "     as an integer from 0-100 inclusive. This is probabilistic,\n"
 	       "     so -w X means each page has an X%% chance of writing\n"
 	       "     and a (100-X)%% chance of reading.\n"
 	       "     (default: 100 i.e. all pages are written to.)\n");
Signature · 1 line
2.38.1
#2 lore raw
Quoted 5 lines · Sean Christopherson
Quoted 1 line · Colin Ian King

There is a spelling mistake in some help text. Fix it.

I assume you have a script/tool of some form to do spell checking? If so, can you point me at it? I'd love to incorporate something like that into my workflow.

https://github.com/ColinIanKing/kernelscan

It needs an appropriate dictionary to be installed. It's very fast (but sometimes makes mistakes, I need to fix those!).

./kernelscan -k src_directory > mistakes.txt

I normally run this across the entire kernel git repo on a daily basis, and diff the new results with the previous results using meld and figure out what needs to be fixed.

You may be better off with using codespell

Colin

Quoted 7 lines

Thanks!

Quoted 2 lines

---

#3 lore raw
Quoted 7 lines · Colin King (gmail)
Quoted 5 lines · Sean Christopherson
Quoted 1 line · Colin Ian King

There is a spelling mistake in some help text. Fix it.

I assume you have a script/tool of some form to do spell checking? If so, can you point me at it? I'd love to incorporate something like that into my workflow.

Quoted 6 lines

https://github.com/ColinIanKing/kernelscan

It needs an appropriate dictionary to be installed. It's very fast (but sometimes makes mistakes, I need to fix those!).

./kernelscan -k src_directory > mistakes.txt

Ah, it's specifically checking messages to avoid false postives on code and whatnot. Neat!

Quoted 5 lines

I normally run this across the entire kernel git repo on a daily basis, and diff the new results with the previous results using meld and figure out what needs to be fixed.

You may be better off with using codespell

Heh, my kind of nitpicking people :-)

MSDOS->MS-DOS

Thanks a ton, that's exactly what I was looking for!

#4 lore raw
Quoted 8 lines · Sean Christopherson
Quoted 1 line · Colin King (gmail)

You may be better off with using codespell

Heh, my kind of nitpicking people :-)

MSDOS->MS-DOS

Thanks a ton, that's exactly what I was looking for!

For anyone following along and/or laughing at me, checkpatch even supports using codespell, e.g.

  ./scripts/checkpatch.pl -g HEAD --codespell
#5 lore raw
Quoted 6 lines · Sean Christopherson
Quoted 5 lines · Sean Christopherson
Quoted 1 line · Colin King (gmail)

You may be better off with using codespell

Heh, my kind of nitpicking people :-)

Quoted 8 lines
Quoted 3 lines
   MSDOS->MS-DOS

Thanks a ton, that's exactly what I was looking for!

For anyone following along and/or laughing at me, checkpatch even supports using codespell, e.g.

   ./scripts/checkpatch.pl -g HEAD --codespell

checkpatch also uses a misspelling dictionary that I occasionally contribute to with common spelling mistakes that I find and fix.

Colin

maintainer Applied
#6 lore raw
In reply to Colin Ian King
Quoted 12 lines · Colin Ian King

There is a spelling mistake in some help text. Fix it.

---
  tools/testing/selftests/kvm/dirty_log_perf_test.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/kvm/dirty_log_perf_test.c +0 -0
index c33e89012ae6..e9d6d1aecf89 100644

tools/testing/selftests/kvm/dirty_log_perf_test.c static void help(char *name) · line 404

Quoted 8 lines
tools/testing/selftests/kvm/dirty_log_perf_test.c +1 -1
@@ -398,7 +398,7 @@ static void help(char *name)
  	printf(" -x: Split the memory region into this number of memslots.\n"
  	       "     (default: 1)\n");
  	printf(" -w: specify the percentage of pages which should be written to\n"
-	       "     as an integer from 0-100 inclusive. This is probabalistic,\n"
+	       "     as an integer from 0-100 inclusive. This is probabilistic,\n"
  	       "     so -w X means each page has an X%% chance of writing\n"
  	       "     and a (100-X)%% chance of reading.\n"
  	       "     (default: 100 i.e. all pages are written to.)\n");

Queued, thanks.

Paolo