Subject: Re: linux-next: duplicate patches in the kvm-arm tree

From: Marc Zyngier <[email-masked]>
Date: Sun, 19 Oct 2025 21:59:11 +0100

On Sun, 19 Oct 2025 21:51:02 +0100,
Stephen Rothwell <[email-masked]> wrote:
> 
> Hi all,
> 
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
> 
>   34f46fecfe96 ("KVM: arm64: selftests: Track width of timer counter as "int", not "uint64_t"")
>   0c5bc849fd76 ("KVM: arm64: selftests: Test effective value of HCR_EL2.AMO")
>   fcaa3f59fda3 ("KVM: arm64: Use the in-context stage-1 in __kvm_find_s1_desc_le
>   5bd5d7d43a92 ("KVM: arm64: nv: Don't advance PC when pending an SVE exception")
>   eea94a0ea55d ("KVM: arm64: nv: Don't treat ZCR_EL2 as a 'mapped' register")
> 
> these are commits
> 
>   cb49b7b8622e ("KVM: arm64: selftests: Track width of timer counter as "int", not "uint64_t"")
>   890c608b4d5e ("KVM: arm64: selftests: Test effective value of HCR_EL2.AMO")
>   a46c09b382ee ("KVM: arm64: Use the in-context stage-1 in __kvm_find_s1_desc_level()")
>   9a1950f97741 ("KVM: arm64: nv: Don't advance PC when pending an SVE exception")
>   ed25dcfbc432 ("KVM: arm64: nv: Don't treat ZCR_EL2 as a 'mapped' register")
> 
> in Linus' tree.

Ah, thanks for the heads up, I forgot to drop those. Now fixed.

Cheers,

	M.

-- 
Without deviation from the norm, progress is not possible.