From: Andrew Morton <akpm@linux-foundation.org>
To: Song Liu <songliubraving@fb.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<kernel-team@fb.com>, Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH] MAINTAINERS: update information for "MEMORY MANAGEMENT"
Date: Wed, 30 Oct 2019 18:21:04 -0700 [thread overview]
Message-ID: <20191030182104.13847e8563105be6cd0a9dfe@linux-foundation.org> (raw)
In-Reply-To: <20191030202217.3498133-1-songliubraving@fb.com>
On Wed, 30 Oct 2019 13:22:17 -0700 Song Liu <songliubraving@fb.com> wrote:
> I was trying to find the mm tree in MAINTAINERS by searching "Morton".
> Unfortunately, I didn't find one. And I didn't even locate the MEMORY
> MANAGEMENT section quickly, because Andrew's name was not listed there.
>
> Thanks to Johannes who helped me find the mm tree.
Oh all right ;)
If I listed everything I "maintain" in MAINTAINERS, I'd double the size
of the dang thing.
q:/usr/src/25> grep "^#NEXT_PATCHES_START" series | wc -l
364
(Those are the identifiable "trees" which I do (or did) "maintain").
But mm/ is special.
> Let save other's time searching around by adding:
>
> M: Andrew Morton <akpm@linux-foundation.org>
> T: git git://github.com/hnaz/linux-mm.git
Also:
--- a/MAINTAINERS~maintainers-update-information-for-memory-management-fix
+++ a/MAINTAINERS
@@ -10523,6 +10523,8 @@ M: Andrew Morton <akpm@linux-foundation.
L: linux-mm@kvack.org
W: http://www.linux-mm.org
T: git git://github.com/hnaz/linux-mm.git
+T: quilt https://ozlabs.org/~akpm/mmotm/
+T: quilt https://ozlabs.org/~akpm/mmots/
S: Maintained
F: include/linux/mm.h
F: include/linux/gfp.h
_
next prev parent reply other threads:[~2019-10-31 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 20:22 Song Liu
2019-10-31 1:21 ` Andrew Morton [this message]
2019-11-05 13:23 ` Mike Rapoport
2019-11-04 14:53 ` Vlastimil Babka
2019-11-04 15:47 ` Johannes Weiner
2019-11-04 15:58 ` Johannes Weiner
2019-11-05 9:45 ` Michal Hocko
2019-11-05 10:14 ` David Hildenbrand
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=20191030182104.13847e8563105be6cd0a9dfe@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=songliubraving@fb.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