From: Vlastimil Babka <vbabka@suse.cz>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Rik van Riel <riel@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
cgroups@vger.kernel.org, Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH] MAINTAINERS, mm: add IRC info and update include file list
Date: Thu, 15 Dec 2016 19:29:36 +0100 [thread overview]
Message-ID: <4d2dcb5e-3908-880c-e8a7-128765f70b91@suse.cz> (raw)
In-Reply-To: <20161215140321.GB27758@node>
On 15.12.2016 15:03, Kirill A. Shutemov wrote:
> On Thu, Dec 15, 2016 at 09:08:48AM +0100, Vlastimil Babka wrote:
>> There's a new C: entry for IRC or similar chat, so add the OFTC #mm channel.
>> While at it, add more F: entries for least the more prominent include/ files
>> related to mm.
>>
>> Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
>> ---
>> MAINTAINERS | 16 ++++++++++++++++
>> 1 file changed, 16 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 59c9895d73d5..fd1ac4bfc2cd 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -3355,6 +3355,7 @@ M: Vladimir Davydov <vdavydov.dev@gmail.com>
>> L: cgroups@vger.kernel.org
>> L: linux-mm@kvack.org
>> S: Maintained
>> +F: include/linux/memcontrol.h
>> F: mm/memcontrol.c
>> F: mm/swap_cgroup.c
>>
>> @@ -8058,12 +8059,27 @@ F: include/uapi/linux/membarrier.h
>> MEMORY MANAGEMENT
>> L: linux-mm@kvack.org
>> W: http://www.linux-mm.org
>> +C: irc://irc.oftc.net/mm
>> S: Maintained
>> F: include/linux/mm.h
>> +F: include/linux/mm_types.h
>> +F: include/linux/mm_inline.h
>> +F: include/linux/mmdebug.h
>> +F: include/linux/compaction.h
>> +F: include/linux/oom.h
>> F: include/linux/gfp.h
>> F: include/linux/mmzone.h
>> F: include/linux/memory_hotplug.h
>> +F: include/linux/mempolicy.h
>> +F: include/linux/page-isolation.h
>> +F: include/linux/page_ext.h
>> +F: include/linux/page_owner.h
>> +F: include/linux/migrate.h
>> +F: include/linux/hugetlb.h
>> +F: include/linux/rmap.h
>> F: include/linux/vmalloc.h
>> +F: include/linux/vmstat.h
>> +F: include/linux/vm_event_item.h
>
> Maybe sort the list?
>
> And the it is still incomplete very incomplete: huge_mm.h, page-flags*,
> mman.h, etc.
Hmm I see.
I wonder if this kind of list scales at all, and how much do we care to have it
complete. Maybe we could use some special keyword with K: and mark the include
files by that instead?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-12-15 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 8:08 Vlastimil Babka
2016-12-15 14:03 ` Kirill A. Shutemov
2016-12-15 18:29 ` Vlastimil Babka [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=4d2dcb5e-3908-880c-e8a7-128765f70b91@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=riel@redhat.com \
--cc=vdavydov.dev@gmail.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