linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	 Dave Hansen <dave.hansen@intel.com>,
	David Hildenbrand <david@redhat.com>,
	 Hugh Dickins <hughd@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	 John Hubbard <jhubbard@nvidia.com>,
	Matthew Wilcox <willy@infradead.org>,
	 Mel Gorman <mel.gorman@gmail.com>,
	Michal Hocko <mhocko@suse.com>,
	 Mike Rapoport <mike.rapoport@gmail.com>,
	 Pasha Tatashin <tatashin@google.com>,
	Peter Xu <peterx@redhat.com>,
	 "Rao, Bharata Bhasker" <bharata@amd.com>,
	Rik van Riel <riel@surriel.com>,
	 Roman Gushchin <roman.gushchin@linux.dev>,
	 Shakeel Butt <shakeel.butt@linux.dev>,
	 "Shutemov, Kirill" <kirill.shutemov@intel.com>,
	Tejun Heo <tj@kernel.org>,  Vlastimil Babka <vbabka@suse.cz>,
	Yang Shi <shy828301@gmail.com>,  Zi Yan <ziy@nvidia.com>,
	Tony Luck <tony.luck@intel.com>,
	 Jason Gunthorpe <jgg@nvidia.com>, Jane Chu <jane.chu@oracle.com>,
	 Miaohe Lin <linmiaohe@huawei.com>,
	Jiaqi Yan <jiaqiyan@google.com>
Cc: linux-mm@kvack.org
Subject: [Invitation] Linux MM Alignment Session on Memory Error Detector on Wednesday
Date: Mon, 28 Oct 2024 14:25:36 -0700 (PDT)	[thread overview]
Message-ID: <9242f7cc-6b9d-b807-9079-db0ca81f3c6d@google.com> (raw)

Hi everybody,

We host a biweekly series, the Linux MM Alignment Session, on Wednesdays.
We'd like to invite MM developers to attend and will announce the topic
for the next instance on the Monday prior to the next meeting.

Our next Linux MM Alignment Session is scheduled for Wednesday.  The
details:

Wednesday, October 30 * 9:00 - 10:00am PDT (GMT-7)
https://meet.google.com/csb-wcds-xya
backup: (US) +1 347-682-5874 PIN: 356 962 072#
international: https://tel.meet/csb-wcds-xya?pin=1301132214803

This week's topic will be supporting Memory Error Detector APIs led by 
Jiaqi Yan.  See 
https://lore.kernel.org/linux-mm/20240924043924.3562257-2-jiaqiyan@google.com/T/

There is lots of interest in these topics, so feel free to forward this 
along to anybody else who may be interested!

Also: if anybody has ideas for future topics, please let me know and I'll
try to organize them.  We'd love to have volunteers to lead future topics
as well as requests for MM topics to be presented.

Looking forward to seeing all of you on Wednesday!


             reply	other threads:[~2024-10-28 21:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 21:25 David Rientjes [this message]
2024-10-28 23:50 ` Jiaqi Yan
2024-11-01 15:08   ` Jiaqi Yan

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=9242f7cc-6b9d-b807-9079-db0ca81f3c6d@google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharata@amd.com \
    --cc=dave.hansen@intel.com \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=jane.chu@oracle.com \
    --cc=jgg@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=jiaqiyan@google.com \
    --cc=kirill.shutemov@intel.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=mel.gorman@gmail.com \
    --cc=mhocko@suse.com \
    --cc=mike.rapoport@gmail.com \
    --cc=peterx@redhat.com \
    --cc=riel@surriel.com \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=shy828301@gmail.com \
    --cc=tatashin@google.com \
    --cc=tj@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --cc=ziy@nvidia.com \
    /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