From: Marc Zyngier <maz@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoffer Dall <cdall@cs.columbia.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the kvm-arm tree
Date: Sun, 19 Oct 2025 21:59:11 +0100 [thread overview]
Message-ID: <86sefewqu8.wl-maz@kernel.org> (raw)
In-Reply-To: <20251020075102.4f6df4fb@canb.auug.org.au>
On Sun, 19 Oct 2025 21:51:02 +0100,
Stephen Rothwell <sfr@canb.auug.org.au> 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.
prev parent reply other threads:[~2025-10-19 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 20:51 linux-next: duplicate patches in the kvm-arm tree Stephen Rothwell
2025-10-19 20:59 ` Marc Zyngier [this message]
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=86sefewqu8.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=cdall@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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