linux-kernel - Re: [PATCH] MAINTAINERS: update information for "MEMORY MANAGEMENT"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191105094518.GA25980@dhcp22.suse.cz>
Date:   Tue, 5 Nov 2019 10:45:18 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Vlastimil Babka <vbabka@...e.cz>
Cc:     Song Liu <songliubraving@...com>, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, kernel-team@...com,
        Johannes Weiner <hannes@...xchg.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: update information for "MEMORY MANAGEMENT"

On Mon 04-11-19 15:53:18, Vlastimil Babka wrote:
[...]
> (And obviously, could we finally get a real git? :)

I would love to see that happen! While I do appreciate existance of
Johannes' mirror that is not something that is suitable for a long term
development IMHO because the tree rebases constantly.

And while we are talking about a better information on the MM
maintainership, should we also be explicit about maintainers of MM parts
which have a primary go to person? At least compaction, allocator, OOM,
memory hotplug, THP, shmem, memory hwpoisoning, early allocators come to
mind.
-- 
Michal Hocko
SUSE Labs