linux-kernel - Re: Updated git tree for MM patches??

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: <13e0466d-d9ec-0efd-f7df-107940636a85@suse.cz>
Date:   Thu, 3 Feb 2022 10:52:35 +0100
From:   Vlastimil Babka <vbabka@...e.cz>
To:     Mike Rapoport <rppt@...ux.ibm.com>,
        Florian Fainelli <f.fainelli@...il.com>
Cc:     Linux Kernel <linux-kernel@...r.kernel.org>,
        Linux Memory Management List <linux-mm@...ck.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Johannes Weiner <hannes@...xchg.org>,
        Mike Kravetz <mike.kravetz@...cle.com>,
        Doug Berger <opendmb@...il.com>,
        Michal Hocko <mhocko@...nel.org>,
        SeongJae Park <sj@...nel.org>,
        Jérôme Glisse <jglisse@...hat.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: Updated git tree for MM patches??

On 2/3/22 08:01, Mike Rapoport wrote:
> On Wed, Feb 02, 2022 at 04:21:38PM -0800, Florian Fainelli wrote:
>> Hi Andrew, Johannes,
>> 
>> The MAINTAINERS file for MEMORY MANAGEMENT lists the following git tree:
>> 
>> git://github.com/hnaz/linux-mm.git
>> 
>> however it does not look like it has been updated in the past 5 months or so
>> as master still points to 5.17-rc7-mm1
>> 
>> Is there another git tree that other memory management related subsystems
>> use for development?
> 
> AFAIK, hnaz/linux-mm was the only git mirror of mmotm series.

IIRC Michal Hocko also used to maintain one, in a different way, but that
was given up even longer ago.

linux-next seems to maintain its branch that's merged to the final next like
this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?h=akpm
but that means getting the whole of next, not just mmotm. Maybe the branch
'akpm-current/current' could be also exposed separately?

> I keep a tree for memblock, but it follows Linus' tree rather than mmotm.
> I think Vlastimil's slab tree does the same.

Yeah as that's how development should be done in general, the trees should
be independent if possible.