All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
	linux-mm@kvack.org, David Hildenbrand <david@kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] MM transition
Date: Fri, 24 Apr 2026 18:49:49 -0700	[thread overview]
Message-ID: <20260425014950.86217-1-sj@kernel.org> (raw)
In-Reply-To: <20260421094216.8dfe14a8c62f2420fa5aace1@linux-foundation.org>

Hello Andrew,

On Tue, 21 Apr 2026 09:42:16 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:

[...]
> mm-next will initially contain mm.git and, I hope, any other git trees
> we can find.  slab and memblock at least temporarily, if Vlastimil and
> Mike are agreeable.  I want other trees in there apart from mm.git so
> the tooling, processes etc can be worked out.

FWIW, I maintain damon/next tree [1] for DAMON patches.  If doing some
experiments with it can help you, please feel free to let me know.  Your mm
trees maintenance is huge help for DAMON development, so I will be happy to
help back.

[1] https://origin.kernel.org/doc/html/latest/mm/damon/maintainer-profile.html#scm-trees


Thanks,
SJ

[...]


      parent reply	other threads:[~2026-04-25  1:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 16:42 [LSF/MM/BPF TOPIC] MM transition Andrew Morton
2026-04-21 19:25 ` Josh Law
2026-04-22 18:18   ` David Hildenbrand (Arm)
2026-04-22 18:22     ` Josh Law
2026-04-22 18:44       ` David Hildenbrand (Arm)
2026-04-22 18:48         ` Josh Law
2026-04-23  6:15           ` Krzysztof Kozlowski
2026-04-22 19:03   ` Matthew Wilcox
2026-04-22 19:13     ` Josh Law
2026-04-23  6:18       ` Krzysztof Kozlowski
2026-04-25  1:49 ` SeongJae Park [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=20260425014950.86217-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.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 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.