From: Sean Christopherson <seanjc@google.com>
To: Rick P Edgecombe <rick.p.edgecombe@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] PUCK Agenda - 2025.03.12 - CANCELED
Date: Tue, 18 Mar 2025 17:21:16 -0700 [thread overview]
Message-ID: <Z9oN_KShuFYnUg5_@google.com> (raw)
In-Reply-To: <6c811b8cf80eebdea921db41d16419919cfa76ae.camel@intel.com>
On Wed, Mar 19, 2025, Rick P Edgecombe wrote:
> On Mon, 2025-03-10 at 09:16 -0700, Sean Christopherson wrote:
> > Paolo and other folks in Europe, would you prefer to cancel PUCK for the rest
> > of March (until Europe joins the US in DST), or deal with the off-by-one error?
>
> Did you guys decide on this?
I haven't heard a peep from anyone. Let's cancel, I already have far too many
meetings this week. I'll send the official notice.
Oh, and I'll cancel for next week as well, as Paolo will be travelling (and for
other reasons).
prev parent reply other threads:[~2025-03-19 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 16:16 [ANNOUNCE] PUCK Agenda - 2025.03.12 - CANCELED Sean Christopherson
2025-03-19 0:09 ` Edgecombe, Rick P
2025-03-19 0:21 ` 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=Z9oN_KShuFYnUg5_@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@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