Re: Process (was Re: [PATCH mm-hotfixes-unstable v18 00/14] khugepaged: add mTHP) collapse support

From: Lorenzo Stoakes

Date: Tue Jun 02 2026 - 08:50:46 EST


On Tue, Jun 02, 2026 at 01:31:35PM +0200, David Hildenbrand (Arm) wrote:
> >> learn from obviously) against how mm works in practice.
> >>
> >> High review load with many overlapping changes might favour a different approach
> >> to a subsystem that looks different from that.
> > Yeah, but as we said, we discussed, it's all rather complicated and we should
> > move incrementally.
> >
>
> Starting to read Documentation/process/maintainer-tip.rst, it's very interesting:
>
> “The tip tree is both a direct development tree and and an aggregation tree for
> several sub-maintainer trees.”
>
> “In general, development against the head of the tip tree master branch is fine,
> but for the subsystems which are maintained separately, have their own git tree
> and are only aggregated into the tip tree, development should take place against
> the relevant subsystem tree or branch.”

Yeah so they have a separate tree model also, so that's an option to learn from
as well!

>
> “Bug fixes which target mainline should always be applicable against the
> mainline kernel tree. Potential conflicts against changes which are already
> queued in the tip tree are handled by the maintainers.”
>
>
> So, yeah, let me reach out to understand what works, what doesn't work, and how
> it works :)

Yes 100% :)

>
> --
> Cheers,
>
> David

Cheers, Lorenzo