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>
Subject: Re: [Invitation] bi-weekly guest_memfd upstream call on 2026-08-19
Date: Wed, 19 Aug 2026 22:11:02 +0200 [thread overview]
Message-ID: <cc0bc18e-1e16-4d73-afdc-b950914b08da@kernel.org> (raw)
In-Reply-To: <54d375aa-8362-4e1c-8f76-bae1eb9f4f76@kernel.org>
On 8/19/26 18:23, David Hildenbrand (Arm) wrote:
> Hi,
>
> Our next guest_memfd upstream call is scheduled for tomorrow, Thursday,
> 2026-08-19 8:00 - 9:00am (GMT-07:00) Pacific Time - Vancouver.
Clarification (thanks David W.): tomorrow is 2026-08-20
--
Cheers,
David
prev parent reply other threads:[~2026-08-19 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 16:23 [Invitation] bi-weekly guest_memfd upstream call on 2026-08-19 David Hildenbrand (Arm)
2026-08-19 17:03 ` David Woodhouse
2026-08-19 20:11 ` David Hildenbrand (Arm) [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=cc0bc18e-1e16-4d73-afdc-b950914b08da@kernel.org \
--to=david@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).