Re: linux-next: manual merge of the mm-nonmm-unstable tree with the mm tree

["David Hildenbrand (Arm)" <david@kernel.org>]

On 9/15/26 19:59, Mark Brown wrote:
> On Tue, Sep 15, 2026 at 10:54:13AM -0700, Andrew Morton wrote:
>> On Tue, 15 Sep 2026 14:32:22 +0100 Mark Brown <broonie@kernel.org> wrote:
> 
>>> from the mm tree and commit:
> 
>> hm, "mm tree" isn't a branch name.  I assume "mm-unstable" was meant.
> 
> No, this is David's tree at:
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/mm/linux.git for-next
> 
> As requested your nonmm branches are the only ones left from your tree,
> they were replaced by the above and the fixes branch at:
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/mm/linux.git for-next-fixes
> 

Yes, only the MM portion go through the MM tree.

I think the problem is that

akpm/mm-nonmm-unstable

is based on

akpm/mm-hotfixes-unstable (and akpm/mm-hotfixes-stable)

Which only go into the MM-next tree.

So if a commit in akpm/mm-hotfixes-unstable changes (and a stale one is in
mm/for-next-fixes), it comes it through two trees in different forms.

Likely we'd need a separate akpm branch for NON-MM hotfixes ... or I'll take
care of all MM hotfixes through the mm/core tree.

-- 
Cheers,

David