From: Sean Christopherson <seanjc@google.com>
To: Vishal Annapurve <vannapurve@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] PUCK Agenda - 2025.03.19 - CANCELED
Date: Wed, 19 Mar 2025 06:25:05 -0700 [thread overview]
Message-ID: <Z9rFsWl96Lc99ZWd@google.com> (raw)
In-Reply-To: <CAGtprH-HmtdyNZnRn3UjA-pBYaBBJgUS7UQSd07PDW94kdwufA@mail.gmail.com>
On Tue, Mar 18, 2025, Vishal Annapurve wrote:
> On Tue, Mar 18, 2025 at 5:24 PM Sean Christopherson <seanjc@google.com> wrote:
> >
> > PUCK is canceled this week due to lack of topics/interest, DST differences, and
> > far too many meetings on my calendar.
>
> We would like to discuss base TDX KVM support readiness for the 6.15
> kernel merge window in the next available session.
The plan is to hold off on merging TDX until 6.16, but to get it into kvm/next
shortly after the 6.15 merge window closes. We want to give it a full cycle in
linux-next so that we're not scrambling to squeeze in the inevitable fixups and
tweaks for such a large series.
prev parent reply other threads:[~2025-03-19 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 0:23 [ANNOUNCE] PUCK Agenda - 2025.03.19 - CANCELED Sean Christopherson
2025-03-19 1:56 ` Vishal Annapurve
2025-03-19 13:25 ` Sean Christopherson [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=Z9rFsWl96Lc99ZWd@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vannapurve@google.com \
/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