Salman Farooq <[email protected]> writes: > Fix two instances of a misspelled word in comments. >
Not sure what this will really get us and what is our maintainer take on such spelling mistake fixes. I definitely hope we won't churn out a lot of patches just to fix simple spell mistakes. But FWIW, the change looks good to me, so: Reviewed-by: Ritesh Harjani (IBM) <[email protected]> > Signed-off-by: Salman Farooq <[email protected]> > --- > arch/powerpc/kvm/book3s_hv_uvmem.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/powerpc/kvm/book3s_hv_uvmem.c > b/arch/powerpc/kvm/book3s_hv_uvmem.c > index 5fbb95d90e99..6ac8364a7639 100644 > --- a/arch/powerpc/kvm/book3s_hv_uvmem.c > +++ b/arch/powerpc/kvm/book3s_hv_uvmem.c > @@ -163,7 +163,7 @@ static DEFINE_SPINLOCK(kvmppc_uvmem_bitmap_lock); > * All its GFNs are moved to Normal-GFNs. > * > * UV_TERMINATE transitions the secure-VM back to normal-VM. All > - * the secure-GFN and shared-GFNs are tranistioned to normal-GFN > + * the secure-GFN and shared-GFNs are transitioned to normal-GFN > * Note: The contents of the normal-GFN is undefined at this point. > * > * GFN state implementation: > @@ -1010,7 +1010,7 @@ static vm_fault_t kvmppc_uvmem_migrate_to_ram(struct > vm_fault *vmf) > /* > * Release the device PFN back to the pool > * > - * Gets called when secure GFN tranistions from a secure-PFN > + * Gets called when secure GFN transitions from a secure-PFN > * to a normal PFN during H_SVM_PAGE_OUT. > * Gets called with kvm->arch.uvmem_lock held. > */ > -- > 2.55.0
