All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: 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>,
	"Mike Rapoport" <rppt@linux.ibm.com>,
	"Vlastimil Babka" <vbabka@suse.cz>
Subject: Re: Updated git tree for MM patches??
Date: Thu,  3 Feb 2022 08:52:00 +0000	[thread overview]
Message-ID: <20220203085200.21490-1-sj@kernel.org> (raw)
In-Reply-To: <fbad2233-207e-6b66-890b-ef1b1f97fdad@gmail.com>

Hi Florian,

On Wed, 2 Feb 2022 16:21:38 -0800 Florian Fainelli <f.fainelli@gmail.com> 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?

I personally fetch and apply the mmotm patches using my simple and buggy
script[1] and periodically upload to my tree[2].

[1] https://github.com/sjp38/mmotm
[2] https://git.kernel.org/sj/h/mmotm-assembled-by-sj


Thanks,
SJ

> 
> Thanks!
> -- 
> Florian
> 

  parent reply	other threads:[~2022-02-03  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  0:21 Updated git tree for MM patches?? Florian Fainelli
2022-02-03  7:01 ` Mike Rapoport
2022-02-03  9:52   ` Vlastimil Babka
2022-02-03  8:52 ` SeongJae Park [this message]
2022-02-03 14:34 ` Johannes Weiner
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=20220203085200.21490-1-sj@kernel.org \
    --to=sj@kernel.org \
    --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=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.