* [PATCH] KVM: arm64: fix typo
@ 2023-05-26 8:15 ` Jun Miao
0 siblings, 0 replies; 4+ messages in thread
From: Jun Miao @ 2023-05-26 8:15 UTC (permalink / raw)
To: maz, oliver.upton, james.morse, linux-arm-kernel; +Cc: kvmarm, jun.miao
Change "begining" to "beginning"
Fixes: 8e6bcc3a4502 ("KVM: arm64: Back the hypervisor 'struct hyp_page' array for all memory")
Signed-off-by: Jun Miao <jun.miao@intel.com>
---
arch/arm64/kvm/hyp/nvhe/mm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/kvm/hyp/nvhe/mm.c b/arch/arm64/kvm/hyp/nvhe/mm.c
index 318298eb3d6b..f16d9f38bb48 100644
--- a/arch/arm64/kvm/hyp/nvhe/mm.c
+++ b/arch/arm64/kvm/hyp/nvhe/mm.c
@@ -145,7 +145,7 @@ int hyp_back_vmemmap(phys_addr_t back)
start = hyp_memory[i].base;
start = ALIGN_DOWN((u64)hyp_phys_to_page(start), PAGE_SIZE);
/*
- * The begining of the hyp_vmemmap region for the current
+ * The beginning of the hyp_vmemmap region for the current
* memblock may already be backed by the page backing the end
* the previous region, so avoid mapping it twice.
*/
--
2.32.0
^ permalink raw reply related [flat|nested] 4+ messages in thread* [PATCH] KVM: arm64: fix typo
@ 2023-05-26 8:15 ` Jun Miao
0 siblings, 0 replies; 4+ messages in thread
From: Jun Miao @ 2023-05-26 8:15 UTC (permalink / raw)
To: maz, oliver.upton, james.morse, linux-arm-kernel; +Cc: kvmarm, jun.miao
Change "begining" to "beginning"
Fixes: 8e6bcc3a4502 ("KVM: arm64: Back the hypervisor 'struct hyp_page' array for all memory")
Signed-off-by: Jun Miao <jun.miao@intel.com>
---
arch/arm64/kvm/hyp/nvhe/mm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/kvm/hyp/nvhe/mm.c b/arch/arm64/kvm/hyp/nvhe/mm.c
index 318298eb3d6b..f16d9f38bb48 100644
--- a/arch/arm64/kvm/hyp/nvhe/mm.c
+++ b/arch/arm64/kvm/hyp/nvhe/mm.c
@@ -145,7 +145,7 @@ int hyp_back_vmemmap(phys_addr_t back)
start = hyp_memory[i].base;
start = ALIGN_DOWN((u64)hyp_phys_to_page(start), PAGE_SIZE);
/*
- * The begining of the hyp_vmemmap region for the current
+ * The beginning of the hyp_vmemmap region for the current
* memblock may already be backed by the page backing the end
* the previous region, so avoid mapping it twice.
*/
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH] KVM: arm64: fix typo
2023-05-26 8:15 ` Jun Miao
@ 2023-05-26 8:35 ` Oliver Upton
-1 siblings, 0 replies; 4+ messages in thread
From: Oliver Upton @ 2023-05-26 8:35 UTC (permalink / raw)
To: Jun Miao; +Cc: maz, oliver.upton, james.morse, linux-arm-kernel, kvmarm
Hi Jun,
The shortlog is too vague. While typo fixes don't need to be
exhaustively described, 'Fix typo' doesn't give any indication as to
where it is.
KVM: arm64: Fix comment typo in hyp_back_vmemmap()
On Fri, May 26, 2023 at 04:15:48PM +0800, Jun Miao wrote:
> Change "begining" to "beginning"
>
> Fixes: 8e6bcc3a4502 ("KVM: arm64: Back the hypervisor 'struct hyp_page' array for all memory")
This is a misuse of the Fixes tag. A typo in a comment is not a bug.
> Signed-off-by: Jun Miao <jun.miao@intel.com>
> ---
> arch/arm64/kvm/hyp/nvhe/mm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kvm/hyp/nvhe/mm.c b/arch/arm64/kvm/hyp/nvhe/mm.c
> index 318298eb3d6b..f16d9f38bb48 100644
> --- a/arch/arm64/kvm/hyp/nvhe/mm.c
> +++ b/arch/arm64/kvm/hyp/nvhe/mm.c
> @@ -145,7 +145,7 @@ int hyp_back_vmemmap(phys_addr_t back)
> start = hyp_memory[i].base;
> start = ALIGN_DOWN((u64)hyp_phys_to_page(start), PAGE_SIZE);
> /*
> - * The begining of the hyp_vmemmap region for the current
> + * The beginning of the hyp_vmemmap region for the current
> * memblock may already be backed by the page backing the end
> * the previous region, so avoid mapping it twice.
> */
> --
> 2.32.0
>
>
--
Thanks,
Oliver
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH] KVM: arm64: fix typo
@ 2023-05-26 8:35 ` Oliver Upton
0 siblings, 0 replies; 4+ messages in thread
From: Oliver Upton @ 2023-05-26 8:35 UTC (permalink / raw)
To: Jun Miao; +Cc: maz, oliver.upton, james.morse, linux-arm-kernel, kvmarm
Hi Jun,
The shortlog is too vague. While typo fixes don't need to be
exhaustively described, 'Fix typo' doesn't give any indication as to
where it is.
KVM: arm64: Fix comment typo in hyp_back_vmemmap()
On Fri, May 26, 2023 at 04:15:48PM +0800, Jun Miao wrote:
> Change "begining" to "beginning"
>
> Fixes: 8e6bcc3a4502 ("KVM: arm64: Back the hypervisor 'struct hyp_page' array for all memory")
This is a misuse of the Fixes tag. A typo in a comment is not a bug.
> Signed-off-by: Jun Miao <jun.miao@intel.com>
> ---
> arch/arm64/kvm/hyp/nvhe/mm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kvm/hyp/nvhe/mm.c b/arch/arm64/kvm/hyp/nvhe/mm.c
> index 318298eb3d6b..f16d9f38bb48 100644
> --- a/arch/arm64/kvm/hyp/nvhe/mm.c
> +++ b/arch/arm64/kvm/hyp/nvhe/mm.c
> @@ -145,7 +145,7 @@ int hyp_back_vmemmap(phys_addr_t back)
> start = hyp_memory[i].base;
> start = ALIGN_DOWN((u64)hyp_phys_to_page(start), PAGE_SIZE);
> /*
> - * The begining of the hyp_vmemmap region for the current
> + * The beginning of the hyp_vmemmap region for the current
> * memblock may already be backed by the page backing the end
> * the previous region, so avoid mapping it twice.
> */
> --
> 2.32.0
>
>
--
Thanks,
Oliver
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-05-26 8:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-05-26 8:15 [PATCH] KVM: arm64: fix typo Jun Miao
2023-05-26 8:15 ` Jun Miao
2023-05-26 8:35 ` Oliver Upton
2023-05-26 8:35 ` Oliver Upton
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.