Re: [PATCH 0/7] MAINTAINERS: MM updates
From: Lorenzo Stoakes (ARM)
Date: Mon Nov 02 2026 - 08:01:43 EST
On Mon, Nov 02, 2026 at 01:32:10PM +0100, David Hildenbrand (Arm) wrote:
> On 11/2/26 12:17, Lorenzo Stoakes (ARM) wrote:
> > On Mon, Nov 02, 2026 at 07:47:46AM +0100, David Hildenbrand (Arm) wrote:
> >> On 11/1/26 21:30, Andrew Morton wrote:
> >>> After that I need to have it whack away at selftests, shudder.
> >>
> >> I am not convinced yet that we want that for all tests, which is why I left it
> >> out. There is too much churn that's not really relevant for a component
> >> maintainer POV.
> >>
> >> I was rather thinking that maybe we'd want a MM selftest component (likely for
> >> the later MISC maintainer) that picks up the usual selftest churn. Component
> >> maintainers really only have to be CCed on functional things.
> >
> > Hmm, but some of these tests are establishing important invariants. I wouldn't
> > want somebody fundamentally changing what the guard region tests do for
> > instance.
> >
> > On the one hand the churn (especially now) is annoying, on the other hand I can
> > just ignore mail I don't care about.
>
> Well, as a listed maintainer you'd be expected to pick up these things.
>
> So I'd much rather have a dedicated selftest maintainer that takes care of these
> things.
>
> OFC we can still add these tests cases to the relevant sections; we just have to
> figure out who will pick up most simple changes.
Yup, files can live in >1 sections at once, which should solve it from both
sides.
--
Cheers, Lorenzo