Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	KVM <kvm@vger.kernel.org>
Cc: ackerleytng@google.com, amit@infradead.org,
	aneeshkumar.kizhakeveetil@arm.com, ashish.kalra@amd.com,
	dwmw2@infradead.org, eberman@quicinc.com, fvdl@google.com,
	gshan@redhat.com, jackmanb@google.com, jackyli@google.com,
	jthoughton@google.com, kalyazin@amazon.com, kas@kernel.org,
	kevinloughlin@google.com, liruxin@google.com,
	michael.day@amd.com, michael.roth@amd.com,
	mike.rapoport@gmail.com, mvaralar@redhat.com,
	pankaj.gupta@amd.com, papaluri@amd.com, patrick.roy@linux.dev,
	Peter Xu <peterx@redhat.com>,
	pheragu@quicinc.com, pkondeti@qti.qualcomm.com, prty@google.com,
	psalian@google.com, qinkun@google.com, seanjc@google.com,
	shan.gavin@gmail.com, shivankg@amd.com, sidtelang@google.com,
	suzuki.poulose@arm.com, tabba@google.com, tatashin@google.com,
	vannapurve@google.com, vbabka@suse.com, wyihan@google.com
Subject: Re: [Invitation] bi-weekly guest_memfd upstream call on 2026-09-17
Date: Wed, 16 Sep 2026 17:16:03 +0200	[thread overview]
Message-ID: <16ffff40-4ef0-4312-a700-348603f05c0c@kernel.org> (raw)
In-Reply-To: <b91dbfae-20f1-4b9f-a25b-4397afae80f9@kernel.org>

On 9/16/26 17:11, David Hildenbrand (Arm) wrote:
> Hi,
> 
> Our next guest_memfd upstream call is scheduled for tomorrow, Thursday,
> 2026-09-16 8:00 - 9:00am (GMT-07:00) Pacific Time - Vancouver.

Sorry, tomorrow (17) of course :(

-- 
Cheers,

David


  reply	other threads:[~2026-09-16 15:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 15:11 [Invitation] bi-weekly guest_memfd upstream call on 2026-09-16 David Hildenbrand (Arm)
2026-09-16 15:16 ` David Hildenbrand (Arm) [this message]
2026-09-17 18:41   ` [Invitation] bi-weekly guest_memfd upstream call on 2026-09-17 Ackerley Tng
2026-09-17 19:30     ` Sean Christopherson
2026-09-18 16:56       ` Ackerley Tng
2026-09-18  9:28     ` Suzuki K Poulose
2026-09-18 16:21       ` Ackerley Tng
2026-09-20 11:22         ` Suzuki K Poulose
2026-09-25  8:40     ` Fuad Tabba

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=16ffff40-4ef0-4312-a700-348603f05c0c@kernel.org \
    --to=david@kernel.org \
    --cc=ackerleytng@google.com \
    --cc=amit@infradead.org \
    --cc=aneeshkumar.kizhakeveetil@arm.com \
    --cc=ashish.kalra@amd.com \
    --cc=dwmw2@infradead.org \
    --cc=eberman@quicinc.com \
    --cc=fvdl@google.com \
    --cc=gshan@redhat.com \
    --cc=jackmanb@google.com \
    --cc=jackyli@google.com \
    --cc=jthoughton@google.com \
    --cc=kalyazin@amazon.com \
    --cc=kas@kernel.org \
    --cc=kevinloughlin@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=liruxin@google.com \
    --cc=michael.day@amd.com \
    --cc=michael.roth@amd.com \
    --cc=mike.rapoport@gmail.com \
    --cc=mvaralar@redhat.com \
    --cc=pankaj.gupta@amd.com \
    --cc=papaluri@amd.com \
    --cc=patrick.roy@linux.dev \
    --cc=peterx@redhat.com \
    --cc=pheragu@quicinc.com \
    --cc=pkondeti@qti.qualcomm.com \
    --cc=prty@google.com \
    --cc=psalian@google.com \
    --cc=qinkun@google.com \
    --cc=seanjc@google.com \
    --cc=shan.gavin@gmail.com \
    --cc=shivankg@amd.com \
    --cc=sidtelang@google.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.com \
    --cc=tatashin@google.com \
    --cc=vannapurve@google.com \
    --cc=vbabka@suse.com \
    --cc=wyihan@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