From: Sean Christopherson <seanjc@google.com>
To: Rick P Edgecombe <rick.p.edgecombe@intel.com>
Cc: "bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"thorsten.blum@linux.dev" <thorsten.blum@linux.dev>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kas@kernel.org" <kas@kernel.org>
Subject: Re: [PATCH RESEND] KVM: TDX: Use struct_size and simplify tdx_get_capabilities
Date: Thu, 13 Nov 2025 10:55:01 -0800 [thread overview]
Message-ID: <aRYphTF5Yjb_Dd-B@google.com> (raw)
In-Reply-To: <4161146b195efee57393b65f8e9022d4bc7e443e.camel@intel.com>
On Thu, Nov 13, 2025, Rick P Edgecombe wrote:
> On Thu, 2025-11-13 at 08:29 -0800, Sean Christopherson wrote:
> > Assuming you're tracking linux-next, I wouldn't bother adding kvm-x86 as kvm-x86/next
> > is fed into linux-next. I do push to topic branches, e.g. kvm-x86/tdx, before
> > merging to kvm-x86/next, but at best you might "gain" a day or two, and the entire
> > reason I do "half" pushes is so that I can run everything through my testing
> > before "officially" publishing it to the world.
> >
> > All in all, explicitly tracking anything kvm-x86 would likely be a net negative.
>
> Yea, linux-next and Linus releases. Ok, we'll leave it. I was just thinking
> about your lack of TDX testing setup, and wondering if it could help. All good.
Heh, I appreciate the offer, but you probably shouldn't encourage my laziness at
this point :-)
next prev parent reply other threads:[~2025-11-13 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 17:16 [PATCH RESEND] KVM: TDX: Use struct_size and simplify tdx_get_capabilities Thorsten Blum
2025-11-12 19:59 ` Edgecombe, Rick P
2025-11-12 20:24 ` Sean Christopherson
2025-11-13 0:41 ` Edgecombe, Rick P
2025-11-13 16:29 ` Sean Christopherson
2025-11-13 18:49 ` Edgecombe, Rick P
2025-11-13 18:55 ` Sean Christopherson [this message]
2025-11-12 21:22 ` Thorsten Blum
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=aRYphTF5Yjb_Dd-B@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=thorsten.blum@linux.dev \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.