All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	James Houghton <jthoughton@google.com>,
	Peter Xu <peterx@redhat.com>,
	Axel Rasmussen <axelrasmussen@google.com>,
	Isaku Yamahata <isaku.yamahata@linux.intel.com>,
	David Matlack <dmatlack@google.com>,
	Yan Zhao <yan.y.zhao@intel.com>, Marc Zyngier <maz@kernel.org>,
	Michael Roth <michael.roth@amd.com>,
	Aaron Lewis <aaronlewis@google.com>
Subject: Re: [ANNOUNCE / RFC] PUCK Future Topics
Date: Thu, 14 Dec 2023 17:11:20 +0000	[thread overview]
Message-ID: <ZXs3OASFnic62LL6@linux.dev> (raw)
In-Reply-To: <20231214001753.779022-1-seanjc@google.com>

On Wed, Dec 13, 2023 at 04:17:53PM -0800, Sean Christopherson wrote:
> Hi all!  There are a handful of PUCK topics that I want to get scheduled, and
> would like your help/input in confirming attendance to ensure we reach critical
> mass.
> 
> If you are on the Cc, please confirm that you are willing and able to attend
> PUCK on the proposed/tentative date for any topics tagged with your name.  Or
> if you simply don't want to attend, I suppose that's a valid answer too. :-)
> 
> If you are not on the Cc but want to ensure that you can be present for a given
> topic, please speak up asap if you have a conflict.  I will do my best to
> accomodate everyone's schedules, and the more warning I get the easier that will
> be.
> 
> Note, the proposed schedule is largely arbitrary, I am not wedded to any
> particular order.  The only known conflict at this time is the guest_memfd()
> post-copy discussion can't land on Jan 10th.
> 
> Thanks!
> 
> 
> 2024.01.03 - Post-copy for guest_memfd()
>     Needs: David M, Paolo, Peter Xu, James, Oliver, Aaron
> 
> 2024.01.10 - Unified uAPI for protected VMs
>     Needs: Paolo, Isaku, Mike R
> 
> 2024.01.17 - Memtypes for non-coherent MDA
>     Needs: Paolo, Yan, Oliver, Marc, more ARM folks?

Can we move this one? I'm traveling 01.08-01.16 and really don't want
to miss this due to jetlag or travel delays.

-- 
Thanks,
Oliver

  parent reply	other threads:[~2023-12-14 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14  0:17 [ANNOUNCE / RFC] PUCK Future Topics Sean Christopherson
2023-12-14  3:32 ` Marc Zyngier
2023-12-14 16:34   ` Sean Christopherson
2023-12-14 17:11 ` Oliver Upton [this message]
2023-12-15 20:13   ` Sean Christopherson
2023-12-18  5:40     ` Yan Zhao
2024-01-09  0:24       ` Jason Gunthorpe
2024-01-09  2:18         ` Yan Zhao
2023-12-15 18:54 ` David Matlack
2024-01-08 23:54 ` Michael Roth

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=ZXs3OASFnic62LL6@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=aaronlewis@google.com \
    --cc=axelrasmussen@google.com \
    --cc=dmatlack@google.com \
    --cc=isaku.yamahata@linux.intel.com \
    --cc=jthoughton@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=michael.roth@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --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 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.