From: Vlastimil Babka <vbabka@suse.cz>
To: Mike Rapoport <rppt@linux.ibm.com>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Mike Kravetz" <mike.kravetz@oracle.com>,
"Doug Berger" <opendmb@gmail.com>,
"Michal Hocko" <mhocko@kernel.org>,
"SeongJae Park" <sj@kernel.org>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: Updated git tree for MM patches??
Date: Thu, 3 Feb 2022 10:52:35 +0100 [thread overview]
Message-ID: <13e0466d-d9ec-0efd-f7df-107940636a85@suse.cz> (raw)
In-Reply-To: <Yft92aSYi9QIfKNf@linux.ibm.com>
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.
next prev parent reply other threads:[~2022-02-03 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 0:21 Florian Fainelli
2022-02-03 7:01 ` Mike Rapoport
2022-02-03 9:52 ` Vlastimil Babka [this message]
2022-02-03 8:52 ` SeongJae Park
[not found] ` <Yfvn2gatF0NA1ihp@cmpxchg.org>
2022-02-03 16:31 ` Florian Fainelli
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=13e0466d-d9ec-0efd-f7df-107940636a85@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=opendmb@gmail.com \
--cc=rppt@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=sj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox