From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"seanjc@google.com" <seanjc@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Zhao, Yan Y" <yan.y.zhao@intel.com>
Subject: Re: [ANNOUNCE] PUCK Agenda - 2024.12.17 *** On Tuesday the 17th!!! ***
Date: Tue, 17 Dec 2024 02:16:08 +0000 [thread overview]
Message-ID: <446cab39966cad7fc4d1824fa81d2ba25b125e69.camel@intel.com> (raw)
In-Reply-To: <Z2DMtr3jdLK9cg34@google.com>
On Mon, 2024-12-16 at 16:58 -0800, Sean Christopherson wrote:
> > Future Schedule:
> > Dec 17th - No topic
Is probably a little late if no one has had the chance to look at it yet, but
hoping we can discuss this ([RFC PATCH 0/2] SEPT SEAMCALL retry proposal):
https://lore.kernel.org/kvm/20241121115139.26338-1-yan.y.zhao@intel.com/
prev parent reply other threads:[~2024-12-17 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 23:58 Sean Christopherson
2024-12-17 0:58 ` Sean Christopherson
2024-12-17 2:16 ` Edgecombe, Rick P [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=446cab39966cad7fc4d1824fa81d2ba25b125e69.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=yan.y.zhao@intel.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
all inboxes | Powered by JetHome®