MAINTAINERS: update MGLRU entry to reflect current status
PATCH 1/1 MAINTAINERS: update MGLRU entry to reflect current status
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in MAINTAINERS, so this doesn't reduce sub-maintainer coverage.
---
(Apologies sent first version of this without MLs attached :)
MAINTAINERS | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
MAINTAINERS +6 -2
@@ -16757,8 +16757,12 @@ F: mm/migrate_device.c MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) M: Andrew Morton <[email protected]> -M: Axel Rasmussen <[email protected]> -M: Yuanchu Xie <[email protected]> +R: Kairui Song <[email protected]> +R: Qi Zheng <[email protected]> +R: Shakeel Butt <[email protected]> +R: Barry Song <[email protected]> +R: Axel Rasmussen <[email protected]> +R: Yuanchu Xie <[email protected]> R: Wei Xu <[email protected]> L: [email protected] S: Maintained
--
2.53.0
+Cc Suren as IIRC he mentioned some intent to look into this as well, in the mmap_lock call.
Quoted 11 lines · Lorenzo Stoakes (Oracle)
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
Seems fair to me.
Quoted 5 lines
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Quoted 7 lines
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>
(I assume the newly added people will ack their additions)
Quoted 28 lines
---
(Apologies sent first version of this without MLs attached :)MAINTAINERS | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)MAINTAINERS +6
-3@@ -16757,8 +16757,12 @@ F: mm/migrate_device.c MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) M: Andrew Morton <[email protected]> -M: Axel Rasmussen <[email protected]> -M: Yuanchu Xie <[email protected]> +R: Kairui Song <[email protected]> +R: Qi Zheng <[email protected]> +R: Shakeel Butt <[email protected]> +R: Barry Song <[email protected]> +R: Axel Rasmussen <[email protected]> +R: Yuanchu Xie <[email protected]> R: Wei Xu <[email protected]> L: [email protected] S: Maintained --2.53.0
David Hildenbrand (Arm)
Acked-byQuoted 26 lines · Vlastimil Babka (SUSE)
+Cc Suren as IIRC he mentioned some intent to look into this as well, in the
mmap_lockcall.Quoted 11 lines · Lorenzo Stoakes (Oracle)
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
Seems fair to me.
Quoted 8 lines
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Quoted 7 lines
Quoted 4 lines
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>
Let's represent the actual situation indeed. People can always become submaintainers again when things changes. For now it's effectively a bit under-maintained.
Quoted 1 line
(I assume the newly added people will ack their additions)
Agreed.
Signature · 3 lines
Cheers, David
Quoted 3 lines · Vlastimil Babka (SUSE)
+Cc Suren as IIRC he mentioned some intent to look into this as well, in the
mmap_lockcall.
Not myself but I asked Kalesh (CC'ed here) to get involved in upstream reviews. Kalesh are you ready to be added as a Reviewer?
Quoted 62 lines · Lorenzo Stoakes (Oracle)
Quoted 11 lines
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
Seems fair to me.
Quoted 5 lines
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Quoted 7 lines
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>(I assume the newly added people will ack their additions)
Quoted 28 lines
---
(Apologies sent first version of this without MLs attached :)MAINTAINERS | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)MAINTAINERS +6
-3@@ -16757,8 +16757,12 @@ F: mm/migrate_device.c MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) M: Andrew Morton <[email protected]> -M: Axel Rasmussen <[email protected]> -M: Yuanchu Xie <[email protected]> +R: Kairui Song <[email protected]> +R: Qi Zheng <[email protected]> +R: Shakeel Butt <[email protected]> +R: Barry Song <[email protected]> +R: Axel Rasmussen <[email protected]> +R: Yuanchu Xie <[email protected]> R: Wei Xu <[email protected]> L: [email protected] S: Maintained --2.53.0
Quoted 9 lines · Suren Baghdasaryan
Quoted 3 lines · Vlastimil Babka (SUSE)
+Cc Suren as IIRC he mentioned some intent to look into this as well, in the
mmap_lockcall.Not myself but I asked Kalesh (CC'ed here) to get involved in upstream reviews. Kalesh are you ready to be added as a Reviewer?
Hi Suren,
Thanks for looping me in. I plan to try my best to dedicate time MGLRU reviewss. Let's see how that goes practically, and we can look at updating the MAINTAINERS file later on if it makes sense.
Thanks,
Kalesh
Quoted 63 lines
Quoted 63 lines · Lorenzo Stoakes (Oracle)
Quoted 11 lines
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
Seems fair to me.
Quoted 5 lines
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Quoted 7 lines
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>(I assume the newly added people will ack their additions)
Quoted 28 lines
---
(Apologies sent first version of this without MLs attached :)MAINTAINERS | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)MAINTAINERS +6
-3@@ -16757,8 +16757,12 @@ F: mm/migrate_device.c MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) M: Andrew Morton <[email protected]> -M: Axel Rasmussen <[email protected]> -M: Yuanchu Xie <[email protected]> +R: Kairui Song <[email protected]> +R: Qi Zheng <[email protected]> +R: Shakeel Butt <[email protected]> +R: Barry Song <[email protected]> +R: Axel Rasmussen <[email protected]> +R: Yuanchu Xie <[email protected]> R: Wei Xu <[email protected]> L: [email protected] S: Maintained --2.53.0
Quoted 11 lines · Kalesh Singh
Quoted 9 lines · Suren Baghdasaryan
Quoted 3 lines · Vlastimil Babka (SUSE)
+Cc Suren as IIRC he mentioned some intent to look into this as well, in the
mmap_lockcall.Not myself but I asked Kalesh (CC'ed here) to get involved in upstream reviews. Kalesh are you ready to be added as a Reviewer?
Quoted 8 lines
Hi Suren,
Thanks for looping me in. I plan to try my best to dedicate time MGLRU reviewss. Let's see how that goes practically, and we can look at updating the
MAINTAINERSfile later on if it makes sense.Thanks,
Kalesh
I think let's wait for you to get involved first, then the road to R: should be pretty quick. And we can see how things go from there :>)
Cheers, Lorenzo
Quoted 18 lines · Lorenzo Stoakes (Oracle)
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Quoted 7 lines
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>
Thanks so much for the trust!
I’m glad to work on MGLRU and help drive progress.
Quoted 17 lines · On Thu, 26 Mar 2026 18:56:29 +0000 "Lorenzo Stoakes (Oracle)" <[email protected]>…
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Quoted 5 lines
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.
All make sense to me.
Quoted 2 lines
Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>
Thanks,
SJ
[...]
Quoted 36 lines · Lorenzo Stoakes (Oracle)
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>---
(Apologies sent first version of this without MLs attached :)MAINTAINERS | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)MAINTAINERS +0
-0
MAINTAINERS F: mm/migrate_device.c · line 16760
Quoted 6 lines
MAINTAINERS +1
-2@@ -16757,8 +16757,12 @@ F: mm/migrate_device.c MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) M: Andrew Morton <[email protected]> -M: Axel Rasmussen <[email protected]> -M: Yuanchu Xie <[email protected]> +R: Kairui Song <[email protected]>
Thanks a lot for the trust, I'm glad and willing to help review and improve MGLRU.
Quoted 35 lines · Lorenzo Stoakes (Oracle)
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>---
(Apologies sent first version of this without MLs attached :)MAINTAINERS | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)MAINTAINERS +0
-0
MAINTAINERS F: mm/migrate_device.c · line 16761
Quoted 7 lines
MAINTAINERS +2
-2@@ -16757,8 +16757,12 @@ F: mm/migrate_device.c MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU) M: Andrew Morton <[email protected]> -M: Axel Rasmussen <[email protected]> -M: Yuanchu Xie <[email protected]> +R: Kairui Song <[email protected]> +R: Qi Zheng <[email protected]>
Thanks a lot for the trust! I'm very glad to work on MGLRU and help with the review.
Thanks,
Qi
Quoted 18 lines · Lorenzo Stoakes (Oracle)
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Quoted 5 lines
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.
Yep, thanks for proposing this change. That all makes sense to me.
Quoted 17 lines · Lorenzo Stoakes (Oracle)
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Quoted 7 lines
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>
Haha, I feel like I am shooting myself in the foot, but if I plan to make drastic changes, then I need to step up and take some responsibility for it.
Quoted 24 lines · Shakeel Butt
Quoted 23 lines · Lorenzo Stoakes (Oracle)
We are moving to a far more proactive model of maintainership within mm and thus put a great deal of emphasis on sub-maintainers being active within the community both in terms of code contributions and review.
The MGLRU has not had much activity since being added to the kernel and the current maintainers who kindly stepped up have unfortunately not been able to contribute a great deal to it for over a year, nor engage all that heavily in review.
As a result, and within no negative connotations implied whatsoever, it seems appropriate to downgrade the current maintainers to reviewers.
At this time nobody is quite exercising the maintainer role in this area of the kernel, but there is encouraging activity from a number of people who are trusted elsewhere in the kernel, and who have contributed relevant work or review.
Therefore add further reviewers, and at this stage - to reflect the reality on the ground - we will not have any sub-maintainers listed at all.
Each of the files listed are shared with other sections in
MAINTAINERS, so this doesn't reduce sub-maintainer coverage.
Quoted 7 lines
Quoted 1 line
Signed-off-by Lorenzo Stoakes (Oracle) <[email protected]>Haha, I feel like I am shooting myself in the foot, but if I plan to make drastic changes, then I need to step up and take some responsibility for it.
Acked-by Shakeel Butt <[email protected]>
It's much appreciated :)
Cheers, Lorenzo