Changs from v1:

 * Add Fixes/Reviewed-by tags (Rick)
 * Add some "backwards" KVM changelog blurbs

--

Sean recently suggested relying on sparse to add type safety in TDX code,
hoping that the robots would notice and complain. Well, that plan is not
working out so great. TDX is not even sparse clean today and nobody seems
to have noticed or cared.

I can see how folks might ignore the 0 vs. NULL complaints. But the
misplaced __user is actually bad enough it should be fixed no matter
what.

Might as well fix it all up.

Cc: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Kirill A. Shutemov" <kas@kernel.org>
Cc: Rick Edgecombe <rick.p.edgecombe@intel.com>
Cc: kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

On Mon, 03 Nov 2025 15:44:35 -0800, Dave Hansen wrote:
> Changs from v1:
> 
>  * Add Fixes/Reviewed-by tags (Rick)
>  * Add some "backwards" KVM changelog blurbs
> 
> --
> 
> [...]

Applied to kvm-x86 tdx, with the scopes changed to "KVM: TDX:".  Thanks!

[1/2] KVM: TDX: Remove __user annotation from kernel pointer
      https://github.com/kvm-x86/linux/commit/228add34dc2f
[2/2] KVM: TDX: Fix sparse warnings from using 0 for NULL
      https://github.com/kvm-x86/linux/commit/27376465e945

--
https://github.com/kvm-x86/linux/tree/next