From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christoffer Dall <cdall@cs•columbia.edu>, Marc Zyngier <maz@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the kvm-arm tree
Date: Mon, 20 Oct 2025 07:51:02 +1100 [thread overview]
Message-ID: <20251020075102.4f6df4fb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-10-19 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 20:51 Stephen Rothwell [this message]
2025-10-19 20:59 ` linux-next: duplicate patches in the kvm-arm tree Marc Zyngier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251020075102.4f6df4fb@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=cdall@cs$(echo .)columbia.edu \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=maz@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox