Skip to contentSkip to conversation

KVM: clean up comments

PATCH In review Tom Rix 2 participants 2 messages Apr 10, 2022 – Apr 20, 2022 KVM

lore
Share & tools
lore

Tom Rix

author
#0 lore raw

PATCH 1/1 KVM: clean up comments

SPDX
*.h use /* */ style comments
*.c use // style comments

Spelling replacements
dimishing to diminishing
memsot to memslot

---
 virt/kvm/dirty_ring.c | 2 +-
 virt/kvm/kvm_main.c   | 4 ++--
 virt/kvm/kvm_mm.h     | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)
virt/kvm/dirty_ring.c +1 -1
index 222ecc81d7df..f4c2a6eb1666 100644
@@ -1,4 +1,4 @@
-/* SPDX-License-Identifier: GPL-2.0-only */
+// SPDX-License-Identifier: GPL-2.0-only
 /*
  * KVM dirty ring implementation
  *
virt/kvm/kvm_main.c +2 -2
index b22f380e3347..90a2ccaa5b25 100644
@@ -662,7 +662,7 @@ void kvm_inc_notifier_count(struct kvm *kvm, unsigned long start,
 		kvm->mmu_notifier_range_end = end;
 	} else {
 		/*
-		 * Fully tracking multiple concurrent ranges has dimishing
+		 * Fully tracking multiple concurrent ranges has diminishing
 		 * returns. Keep things simple and just find the minimal range
 		 * which includes the current and new ranges. As there won't be
 		 * enough information to subtract a range after its invalidate
@@ -1793,7 +1793,7 @@ static int kvm_set_memslot(struct kvm *kvm,
 
 	/*
 	 * No need to refresh new->arch, changes after dropping slots_arch_lock
-	 * will directly hit the final, active memsot.  Architectures are
+	 * will directly hit the final, active memslot.  Architectures are
 	 * responsible for knowing that new->arch may be stale.
 	 */
 	kvm_commit_memory_region(kvm, old, new, change);
virt/kvm/kvm_mm.h +1 -1
index 34ca40823260..41da467d99c9 100644
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.0-only
+/* SPDX-License-Identifier: GPL-2.0-only */
 
 #ifndef __KVM_MM_H__
 #define __KVM_MM_H__ 1
Signature · 1 line
2.27.0