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-04-03
Date: Tue, 1 Apr 2025 22:55:21 +0200 [thread overview]
Message-ID: <6c9362f3-0eb8-4526-a7d3-3d483a40dd84@redhat.com> (raw)
In-Reply-To: <7b3090fb-1816-4761-a7a5-17d49a050645@redhat.com>
On 01.04.25 20:46, David Hildenbrand wrote:
> Hi everybody,
>
> our next guest_memfd upstream call is scheduled for Thursday,
> 2025-04-03 at 8:00 - 9:00am (GMT-08:00) Pacific Time - Vancouver.
Correction (thanks James!)
8:00 - 9:00am (GMT-07:00) Pacific Time - Vancouver.
is the real deal according to google calendar.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-04-01 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 18:46 David Hildenbrand
2025-04-01 20:55 ` 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=6c9362f3-0eb8-4526-a7d3-3d483a40dd84@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