From: Ira Weiny <ira.weiny@intel.com>
To: David Hildenbrand <david@redhat.com>,
Ira Weiny <ira.weiny@intel.com>,
"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-07-17
Date: Fri, 18 Jul 2025 13:17:55 -0500 [thread overview]
Message-ID: <687a8fd38e118_3c6f1d29415@iweiny-mobl.notmuch> (raw)
In-Reply-To: <eb6afc50-10e1-4326-95a6-6415f407c887@redhat.com>
David Hildenbrand wrote:
> On 18.07.25 00:14, Ira Weiny wrote:
> > David Hildenbrand wrote:
> >> Hi everybody,
> >>
> >> I had to move the meeting by one week -- I'll be out the next two days
> >> -- and decided to send the invite out already to highlight that :)
> >>
> >> So, our next guest_memfd upstream call is scheduled for next week,
> >> Thursday, 2025-07-17 at 8:00 - 9:00am (GMT-07:00) Pacific Time - Vancouver.
> >
> > Did I hear correctly? I thought I heard you mentioned that we are meeting
> > again in a week? So was today, 7/17, a one off shift of the bi-weekly call?
> >
> > Or do we now meet 2 weeks from today?
>
> So, the plan was to only move a single meeting (last week to this week)
> and to continue next week with the ordinary schedule.
>
> So I am planning on sending out an invite next week for the meeting next
> week (July 24).
That works! Thanks for the clarification,
Ira
prev parent reply other threads:[~2025-07-18 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 20:32 [Invitation] bi-weekly guest_memfd upstream call on 2025-07-17 David Hildenbrand
2025-07-17 22:14 ` Ira Weiny
2025-07-18 7:41 ` David Hildenbrand
2025-07-18 18:17 ` Ira Weiny [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=687a8fd38e118_3c6f1d29415@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=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).