From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Sean Christopherson <seanjc@google•com>
Cc: Paolo Bonzini <pbonzini@redhat•com>,
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-x86 tree
Date: Tue, 17 Oct 2023 15:37:19 +1100 [thread overview]
Message-ID: <20231017153719.28884723@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
afb2c7e27a7f ("KVM: selftests: Force load all supported XSAVE state in state test")
d7b8762ec4a3 ("KVM: selftests: Load XSAVE state into untouched vCPU during state test")
ff0654c71fb6 ("KVM: selftests: Touch relevant XSAVE state in guest for state test")
27526efb5cff ("KVM: x86: Constrain guest-supported xfeatures only at KVM_GET_XSAVE{2}")
2d287ec65e79 ("x86/fpu: Allow caller to constrain xfeatures when copying to uabi buffer")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-10-17 4:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 4:37 Stephen Rothwell [this message]
2023-10-17 16:34 ` linux-next: duplicate patches in the kvm-x86 tree Sean Christopherson
-- strict thread matches above, loose matches on Subject: below --
2025-03-02 4:24 Stephen Rothwell
2024-07-19 3:44 Stephen Rothwell
2024-07-19 13:21 ` Sean Christopherson
2023-09-08 0:18 Stephen Rothwell
2023-09-08 1:18 ` Sean Christopherson
2023-01-24 1:55 Stephen Rothwell
2023-01-24 8:46 ` Marc Zyngier
2023-01-24 11:09 ` Paolo Bonzini
2023-01-24 16:15 ` Sean Christopherson
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=20231017153719.28884723@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pbonzini@redhat$(echo .)com \
--cc=seanjc@google$(echo .)com \
/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