linux-kernel - [GIT PULL (sort of)] KVM: x86: fixes and selftests fixes/cleanups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240213005710.672448-1-seanjc@google.com>
Date: Mon, 12 Feb 2024 16:57:10 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Sean Christopherson <seanjc@...gle.com>
Subject: [GIT PULL (sort of)] KVM: x86: fixes and selftests fixes/cleanups

I have two pull requests for 6.8, but I goofed (or maybe raced with you
pushing to kvm/master), and based everything on 6.8-rc2 instead of 6.8-rc1 as
you did.  And so of course the pull requests would bring in waaaaay more than
just the intended KVM changes.

Can I bribe you to do a back merge of 6.8-rc2, so that my pull requests don't
make me look like a complete idiot?

It's not the end of the world for me to rebase, but I'd prefer not to throw
away the hashes and the time the commits have spent in -next.

FWIW, the two tags are:

 https://github.com/kvm-x86/linux.git tags/kvm-x86-fixes-6.8-rcN
 https://github.com/kvm-x86/linux.git tags/kvm-x86-selftests-6.8-rcN