[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-523319d8-fda9-4737-9c43-d54bcfd7a7f2@palmer-ri-x1c9>
Date: Wed, 01 Jun 2022 21:26:40 -0700 (PDT)
From: Palmer Dabbelt <palmer@...belt.com>
To: Julia.Lawall@...ia.fr, anup@...infault.org
CC: kernel-janitors@...r.kernel.org, atishp@...shpatra.org,
Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, kvm@...r.kernel.org,
kvm-riscv@...ts.infradead.org, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: (RISC-V KVM) Re: [PATCH] RISC-V: fix typos in comments
On Sat, 30 Apr 2022 12:11:20 PDT (-0700), Julia.Lawall@...ia.fr wrote:
> Various spelling mistakes in comments.
> Detected with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@...ia.fr>
>
> ---
> arch/riscv/kvm/vmid.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/riscv/kvm/vmid.c b/arch/riscv/kvm/vmid.c
> index 2fa4f7b1813d..4a2178c60b5d 100644
> --- a/arch/riscv/kvm/vmid.c
> +++ b/arch/riscv/kvm/vmid.c
> @@ -92,7 +92,7 @@ void kvm_riscv_stage2_vmid_update(struct kvm_vcpu *vcpu)
> * We ran out of VMIDs so we increment vmid_version and
> * start assigning VMIDs from 1.
> *
> - * This also means existing VMIDs assignement to all Guest
> + * This also means existing VMIDs assignment to all Guest
> * instances is invalid and we have force VMID re-assignement
> * for all Guest instances. The Guest instances that were not
> * running will automatically pick-up new VMIDs because will
Anup: I'm guessing you didn't see this because it didn't have KVM in the
subject?
Reviewed-by: Palmer Dabbelt <palmer@...osinc.com>
Acked-by: Palmer Dabbelt <palmer@...osinc.com>
if that helps any, I don't see in anywhere but not sure if I'm just
missing it.
Powered by blists - more mailing lists