From: Johannes Weiner <hannes@cmpxchg.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: helpdesk@kernel.org, "Andrew Morton" <akpm@linux-foundation.org>,
"Naoya Horiguchi" <naoya.horiguchi@nec.com>,
"Michal Hocko" <mhocko@kernel.org>,
"Vladimir Davydov" <vdavydov.dev@gmail.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Mike Kravetz" <mike.kravetz@oracle.com>,
"Mike Rapoport" <rppt@linux.ibm.com>,
"Will Deacon" <will@kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
"Nick Piggin" <npiggin@gmail.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Dennis Zhou" <dennis@kernel.org>, "Tejun Heo" <tj@kernel.org>,
"Christoph Lameter" <cl@linux.com>,
"David Rientjes" <rientjes@google.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Hugh Dickins" <hughd@google.com>,
linux-mm@kvack.org
Subject: Re: Create mm@lists.linux.dev
Date: Thu, 10 Jun 2021 15:44:19 -0400 [thread overview]
Message-ID: <YMJrk81oZa5ArWPw@cmpxchg.org> (raw)
In-Reply-To: <YMJLJR/atypu++qU@casper.infradead.org>
On Thu, Jun 10, 2021 at 06:25:57PM +0100, Matthew Wilcox wrote:
> Address : mm@lists.linux.dev
> Description: Linux Memory Management
> Owners : bcrl@kvack.org, willy@infradead.org, vbabka@suse.cz
> Allow HTML : N
> Archives : Y
>
> Reasons for the list and additional info:
> kvack.org has been regrettably unreliable recently, and it makes sense
> to have a full-time sysadmin who can fix issues without being forced to
> drive for five hours to the colo.
Agreed.
It was eating my email too in the past, and I spent a lot of time
making speculative changes to my setup to get it to work. We may as
well take advantage of the infrastructure used by most every other
subsystem already, and avoid this pain for both users and owners.
Thanks for pushing for this
next parent reply other threads:[~2021-06-10 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YMJLJR/atypu++qU@casper.infradead.org>
2021-06-10 19:44 ` Johannes Weiner [this message]
2021-06-14 14:25 ` Create mm@lists.linux.dev Jason Gunthorpe
2021-06-15 11:19 ` Christoph Lameter
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=YMJrk81oZa5ArWPw@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=helpdesk@kernel.org \
--cc=hughd@google.com \
--cc=jglisse@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=rppt@linux.ibm.com \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=will@kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.