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-03-19
Date: Thu, 19 Mar 2026 07:05:07 +0100 [thread overview]
Message-ID: <7b7d07c7-7717-404e-b2f8-772987523efd@kernel.org> (raw)
In-Reply-To: <22d1bdf9-4d21-4252-8558-e9618a409bc5@kernel.org>
On 3/18/26 11:50, David Hildenbrand (Arm) wrote:
> Hi,
>
> Our next guest_memfd upstream call is scheduled for tomorrow, Thursday,
> 2026-03-19 at 8:00 - 9:00am (GMT-07:00) Pacific Time - Vancouver.
>
> !!! Note the GMT-08:00 -> GMT-07:00 change due to DST in the US :) !!!
As Google calendar keeps dropping all invitees from the meeting for some
reason at random points in time--I suspect because I moved the calendar
entry over from my RH account by changing the owner--I just created a
new calendar entry and sent out invitations.
Hopefully it sticks now ...
--
Cheers,
David
prev parent reply other threads:[~2026-03-19 6:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 10:50 [Invitation] bi-weekly guest_memfd upstream call on 2026-03-19 David Hildenbrand (Arm)
2026-03-19 6:05 ` 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=7b7d07c7-7717-404e-b2f8-772987523efd@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