From: Amit Shah <amit@infradead.org>
To: Ackerley Tng <ackerleytng@google.com>,
David Hildenbrand <david@redhat.com>
Cc: linux-coco@lists.linux.dev, kvm@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Proposal: bi-weekly guest_memfd upstream call
Date: Fri, 15 Nov 2024 14:18:27 +0100 [thread overview]
Message-ID: <9447b7b512627a505396799080f45bf0596ef9c5.camel@infradead.org> (raw)
In-Reply-To: <diqzmsieybwf.fsf@ackerleytng-ctop-specialist.c.googlers.com>
On Mon, 2024-11-04 at 20:36 +0000, Ackerley Tng wrote:
> David Hildenbrand <david@redhat.com> writes:
>
> > Ahoihoi,
> >
> > while talking to a bunch of folks at LPC about guest_memfd, it was
> > raised that there isn't really a place for people to discuss the
> > development of guest_memfd on a regular basis.
[...]
Please add me to the meeting invite.
Thanks,
Amit
prev parent reply other threads:[~2024-11-15 13:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 13:39 Proposal: bi-weekly guest_memfd upstream call David Hildenbrand
2024-10-10 14:20 ` Vishal Annapurve
2024-10-11 20:01 ` Michael Roth
2024-10-10 14:30 ` Fuad Tabba
2024-10-10 14:38 ` David Hildenbrand
2024-10-10 17:14 ` Ackerley Tng
2024-10-11 11:50 ` David Hildenbrand
2024-10-11 15:15 ` Sean Christopherson
2024-10-11 17:48 ` Ackerley Tng
2024-10-14 9:05 ` Vlastimil Babka
2024-10-14 9:34 ` David Hildenbrand
2024-10-11 17:57 ` Dan Williams
2024-10-12 3:58 ` Gupta, Pankaj
2024-10-15 10:24 ` Patrick Roy
2024-10-16 9:31 ` Suzuki K Poulose
2024-10-16 10:58 ` Gavin Shan
2024-10-21 8:05 ` Kalra, Ashish
2024-11-04 20:36 ` Ackerley Tng
2024-11-14 16:29 ` David Hildenbrand
2024-11-15 13:18 ` Amit Shah [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=9447b7b512627a505396799080f45bf0596ef9c5.camel@infradead.org \
--to=amit@infradead.org \
--cc=ackerleytng@google.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).