* [Invitation] bi-weekly guest_memfd upstream call on 2025-07-17
@ 2025-07-08 20:32 David Hildenbrand
2025-07-17 22:14 ` Ira Weiny
0 siblings, 1 reply; 4+ messages in thread
From: David Hildenbrand @ 2025-07-08 20:32 UTC (permalink / raw)
To: linux-coco@lists.linux.dev, linux-mm@kvack.org, KVM
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.
We'll be using the following Google meet:
http://meet.google.com/wxp-wtju-jzw
The meeting notes can be found at [1], where we also link recordings and
collect current guest_memfd upstream proposals. If you want an google
calendar invitation that also covers all future meetings, just write me
a mail.
In this meeting, we'll talk about memory failure handling, and continue
our discussion on polishing up mmap support ("stage-1") to finally get
it merged ... and whatever else comes up around that.
To put something to discuss onto the agenda, reply to this mail or add
them to the "Topics/questions for next meeting(s)" section in the
meeting notes as a comment.
Cheers,
David
[1]
https://docs.google.com/document/d/1M6766BzdY1Lhk7LiR5IqVR8B8mG3cr-cxTxOrAosPOk/edit?usp=sharing
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Invitation] bi-weekly guest_memfd upstream call on 2025-07-17
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
0 siblings, 1 reply; 4+ messages in thread
From: Ira Weiny @ 2025-07-17 22:14 UTC (permalink / raw)
To: David Hildenbrand, linux-coco@lists.linux.dev, linux-mm@kvack.org,
KVM
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?
Ira
>
> We'll be using the following Google meet:
> http://meet.google.com/wxp-wtju-jzw
>
> The meeting notes can be found at [1], where we also link recordings and
> collect current guest_memfd upstream proposals. If you want an google
> calendar invitation that also covers all future meetings, just write me
> a mail.
>
> In this meeting, we'll talk about memory failure handling, and continue
> our discussion on polishing up mmap support ("stage-1") to finally get
> it merged ... and whatever else comes up around that.
>
> To put something to discuss onto the agenda, reply to this mail or add
> them to the "Topics/questions for next meeting(s)" section in the
> meeting notes as a comment.
>
> Cheers,
>
> David
>
> [1]
> https://docs.google.com/document/d/1M6766BzdY1Lhk7LiR5IqVR8B8mG3cr-cxTxOrAosPOk/edit?usp=sharing
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Invitation] bi-weekly guest_memfd upstream call on 2025-07-17
2025-07-17 22:14 ` Ira Weiny
@ 2025-07-18 7:41 ` David Hildenbrand
2025-07-18 18:17 ` Ira Weiny
0 siblings, 1 reply; 4+ messages in thread
From: David Hildenbrand @ 2025-07-18 7:41 UTC (permalink / raw)
To: Ira Weiny, linux-coco@lists.linux.dev, linux-mm@kvack.org, KVM
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).
--
Cheers,
David / dhildenb
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Invitation] bi-weekly guest_memfd upstream call on 2025-07-17
2025-07-18 7:41 ` David Hildenbrand
@ 2025-07-18 18:17 ` Ira Weiny
0 siblings, 0 replies; 4+ messages in thread
From: Ira Weiny @ 2025-07-18 18:17 UTC (permalink / raw)
To: David Hildenbrand, Ira Weiny, linux-coco@lists.linux.dev,
linux-mm@kvack.org, KVM
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2025-07-18 18:16 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).