From: David Hildenbrand <david@redhat.com>
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 2025-09-04
Date: Wed, 3 Sep 2025 17:51:17 +0200 [thread overview]
Message-ID: <586a6b30-f4e2-494a-b83e-08c1b01b4197@redhat.com> (raw)
In-Reply-To: <5d1bf8ef-5f30-4962-bbd3-d698c0e9b7fe@redhat.com>
On 03.09.25 09:06, David Hildenbrand wrote:
> Hi everybody,
>
> Our next guest_memfd upstream call is scheduled for tomorrow, Thursday,
> 2025-09-04 at 8:00 - 9:00am (GMT-07:00) Pacific Time - Vancouver.
Change of plans: Fuad reminded me that tomorrow is KVM forum (guess
who's not going ;) ), so it's probably best to skip this one.
Talk to you in two weeks then!
--
Cheers
David / dhildenb
prev parent reply other threads:[~2025-09-03 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 7:06 [Invitation] bi-weekly guest_memfd upstream call on 2025-09-04 David Hildenbrand
2025-09-03 15:51 ` David Hildenbrand [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=586a6b30-f4e2-494a-b83e-08c1b01b4197@redhat.com \
--to=david@redhat.com \
--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).