Similar to and just below the existing MAPLE TREE entry.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Liam: I'm not sure what you prefer for the MAINTAINERS entry, so let me
know if you want anything changed. There are also a few other options,
for example, I could just add the files under the existing MAPLE TREE
entry? The get_maintainers script should still send any relevant patches
my way because they also match the RUST entry that has a wildcard on the
rust/ directory.
Which tree does maple tree patches usually land through?
Andrew Ballance: You mentioned being interested in being listed here as
well?
---
MAINTAINERS | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 26053163fe5aed2fc4b4e39d47062c93b873ac13..4a52d884e36eafe1c819227207123c51caf02ee5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14674,6 +14674,16 @@ F: lib/test_maple_tree.c
F: tools/testing/radix-tree/maple.c
F: tools/testing/shared/linux/maple_tree.h
+MAPLE TREE [RUST]
+M: Liam R. Howlett <Liam.Howlett@oracle.com>
+M: Alice Ryhl <aliceryhl@google.com>
+L: maple-tree@lists.infradead.org
+L: linux-mm@kvack.org
+L: rust-for-linux@vger.kernel.org
+S: Supported
+F: rust/helpers/maple_tree.c
+F: rust/kernel/maple_tree.rs
+
MARDUK (CREATOR CI40) DEVICE TREE SUPPORT
M: Rahul Bedarkar <rahulbedarkar89@gmail.com>
L: linux-mips@vger.kernel.org
--
2.51.0.rc1.167.g924127e9c0-googOn 8/19/25 5:34 AM, Alice Ryhl wrote: > Similar to and just below the existing MAPLE TREE entry. > > Signed-off-by: Alice Ryhl <aliceryhl@google.com> > --- > Liam: I'm not sure what you prefer for the MAINTAINERS entry, so let me > know if you want anything changed. There are also a few other options, > for example, I could just add the files under the existing MAPLE TREE > entry? The get_maintainers script should still send any relevant patches > my way because they also match the RUST entry that has a wildcard on the > rust/ directory. > > Which tree does maple tree patches usually land through? > > Andrew Ballance: You mentioned being interested in being listed here as > well? Yes, please add me as a maintainer. In regards to the discussion about the maintainers entry, personally I would prefer that the entries for the rust and c were separate, just like the version in this patch. > --- > MAINTAINERS | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 26053163fe5aed2fc4b4e39d47062c93b873ac13..4a52d884e36eafe1c819227207123c51caf02ee5 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -14674,6 +14674,16 @@ F: lib/test_maple_tree.c > F: tools/testing/radix-tree/maple.c > F: tools/testing/shared/linux/maple_tree.h > > +MAPLE TREE [RUST] > +M: Liam R. Howlett <Liam.Howlett@oracle.com> > +M: Alice Ryhl <aliceryhl@google.com> > +L: maple-tree@lists.infradead.org > +L: linux-mm@kvack.org > +L: rust-for-linux@vger.kernel.org > +S: Supported > +F: rust/helpers/maple_tree.c > +F: rust/kernel/maple_tree.rs > + > MARDUK (CREATOR CI40) DEVICE TREE SUPPORT > M: Rahul Bedarkar <rahulbedarkar89@gmail.com> > L: linux-mips@vger.kernel.org > Best Regards, Andrew Ballance
On Tue Aug 19, 2025 at 12:34 PM CEST, Alice Ryhl wrote: > Similar to and just below the existing MAPLE TREE entry. > > Signed-off-by: Alice Ryhl <aliceryhl@google.com> > --- > Liam: I'm not sure what you prefer for the MAINTAINERS entry, so let me > know if you want anything changed. There are also a few other options, > for example, I could just add the files under the existing MAPLE TREE > entry? The get_maintainers script should still send any relevant patches > my way because they also match the RUST entry that has a wildcard on the > rust/ directory. From v1 [1]: >> We should have another section for the maple tree, since it's not just >> used for mm. Your stated plan is to use it for GPU allocations and the >> code doesn't live in mm/, wdyt? > Sure, I can add a new section if you prefer that. Maple tree is already used outside of mm, e.g. for regmap stuff and I also use it in nouveau. Hence, I read this as moving maple tree to e.g. lib/ adjusting the existing entry. I personally think that - of course unless the affected people prefer otherwise - it is usually best to keep a single maintainers entry for the C and the Rust code. Maybe Alice can simply be added to the existing maintainers entry? What do you think? [1] https://lore.kernel.org/all/aJW3L3SEVUl_AVvN@google.com/ > Which tree does maple tree patches usually land through? > > Andrew Ballance: You mentioned being interested in being listed here as > well? > --- > MAINTAINERS | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 26053163fe5aed2fc4b4e39d47062c93b873ac13..4a52d884e36eafe1c819227207123c51caf02ee5 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -14674,6 +14674,16 @@ F: lib/test_maple_tree.c > F: tools/testing/radix-tree/maple.c > F: tools/testing/shared/linux/maple_tree.h > > +MAPLE TREE [RUST] > +M: Liam R. Howlett <Liam.Howlett@oracle.com> > +M: Alice Ryhl <aliceryhl@google.com> > +L: maple-tree@lists.infradead.org > +L: linux-mm@kvack.org > +L: rust-for-linux@vger.kernel.org > +S: Supported > +F: rust/helpers/maple_tree.c > +F: rust/kernel/maple_tree.rs > + > MARDUK (CREATOR CI40) DEVICE TREE SUPPORT > M: Rahul Bedarkar <rahulbedarkar89@gmail.com> > L: linux-mips@vger.kernel.org > > -- > 2.51.0.rc1.167.g924127e9c0-goog
* Danilo Krummrich <dakr@kernel.org> [250819 07:49]: > On Tue Aug 19, 2025 at 12:34 PM CEST, Alice Ryhl wrote: > > Similar to and just below the existing MAPLE TREE entry. > > > > Signed-off-by: Alice Ryhl <aliceryhl@google.com> > > --- > > Liam: I'm not sure what you prefer for the MAINTAINERS entry, so let me > > know if you want anything changed. There are also a few other options, > > for example, I could just add the files under the existing MAPLE TREE > > entry? The get_maintainers script should still send any relevant patches > > my way because they also match the RUST entry that has a wildcard on the > > rust/ directory. > > From v1 [1]: > > >> We should have another section for the maple tree, since it's not just > >> used for mm. Your stated plan is to use it for GPU allocations and the > >> code doesn't live in mm/, wdyt? > > > Sure, I can add a new section if you prefer that. > > Maple tree is already used outside of mm, e.g. for regmap stuff and I also use > it in nouveau. Hence, I read this as moving maple tree to e.g. lib/ adjusting > the existing entry. > > I personally think that - of course unless the affected people prefer otherwise > - it is usually best to keep a single maintainers entry for the C and the Rust > code. Maybe Alice can simply be added to the existing maintainers entry? > > What do you think? I'm not sure what you mean by lib/ since the lib files are spread into other entries by the looks of it? I'm okay with the entry below or adjusting the existing one. > > [1] https://lore.kernel.org/all/aJW3L3SEVUl_AVvN@google.com/ > > > Which tree does maple tree patches usually land through? > > > > Andrew Ballance: You mentioned being interested in being listed here as > > well? > > --- > > MAINTAINERS | 10 ++++++++++ > > 1 file changed, 10 insertions(+) > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > index 26053163fe5aed2fc4b4e39d47062c93b873ac13..4a52d884e36eafe1c819227207123c51caf02ee5 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -14674,6 +14674,16 @@ F: lib/test_maple_tree.c > > F: tools/testing/radix-tree/maple.c > > F: tools/testing/shared/linux/maple_tree.h > > > > +MAPLE TREE [RUST] > > +M: Liam R. Howlett <Liam.Howlett@oracle.com> > > +M: Alice Ryhl <aliceryhl@google.com> > > +L: maple-tree@lists.infradead.org > > +L: linux-mm@kvack.org > > +L: rust-for-linux@vger.kernel.org > > +S: Supported > > +F: rust/helpers/maple_tree.c > > +F: rust/kernel/maple_tree.rs > > + > > MARDUK (CREATOR CI40) DEVICE TREE SUPPORT > > M: Rahul Bedarkar <rahulbedarkar89@gmail.com> > > L: linux-mips@vger.kernel.org > > > > -- > > 2.51.0.rc1.167.g924127e9c0-goog > >
On Tue, Aug 19, 2025 at 09:36:10AM -0400, Liam R. Howlett wrote: > * Danilo Krummrich <dakr@kernel.org> [250819 07:49]: > > On Tue Aug 19, 2025 at 12:34 PM CEST, Alice Ryhl wrote: > > > Similar to and just below the existing MAPLE TREE entry. > > > > > > Signed-off-by: Alice Ryhl <aliceryhl@google.com> > > > --- > > > Liam: I'm not sure what you prefer for the MAINTAINERS entry, so let me > > > know if you want anything changed. There are also a few other options, > > > for example, I could just add the files under the existing MAPLE TREE > > > entry? The get_maintainers script should still send any relevant patches > > > my way because they also match the RUST entry that has a wildcard on the > > > rust/ directory. > > > > From v1 [1]: > > > > >> We should have another section for the maple tree, since it's not just > > >> used for mm. Your stated plan is to use it for GPU allocations and the > > >> code doesn't live in mm/, wdyt? > > > > > Sure, I can add a new section if you prefer that. > > > > Maple tree is already used outside of mm, e.g. for regmap stuff and I also use > > it in nouveau. Hence, I read this as moving maple tree to e.g. lib/ adjusting > > the existing entry. > > > > I personally think that - of course unless the affected people prefer otherwise > > - it is usually best to keep a single maintainers entry for the C and the Rust > > code. Maybe Alice can simply be added to the existing maintainers entry? > > > > What do you think? > > I'm not sure what you mean by lib/ since the lib files are spread into > other entries by the looks of it? > > I'm okay with the entry below or adjusting the existing one. In that case, I suggest we do this: MAPLE TREE M: Liam R. Howlett <Liam.Howlett@oracle.com> +R: Alice Ryhl <aliceryhl@google.com> +R: Andrew Ballance <andrewjballance@gmail.com> L: maple-tree@lists.infradead.org L: linux-mm@kvack.org S: Supported F: Documentation/core-api/maple_tree.rst F: include/linux/maple_tree.h F: include/trace/events/maple_tree.h F: lib/maple_tree.c F: lib/test_maple_tree.c +F: rust/helpers/maple_tree.c +F: rust/kernel/maple_tree.rs F: tools/testing/radix-tree/maple.c F: tools/testing/shared/linux/maple_tree.h Optionally we could add (RUST) similar to the LOCKING PRIMITIVES maintainers entry. Thoughts? Alice
On Tue Aug 19, 2025 at 3:36 PM CEST, Liam R. Howlett wrote: > * Danilo Krummrich <dakr@kernel.org> [250819 07:49]: >> On Tue Aug 19, 2025 at 12:34 PM CEST, Alice Ryhl wrote: >> > Similar to and just below the existing MAPLE TREE entry. >> > >> > Signed-off-by: Alice Ryhl <aliceryhl@google.com> >> > --- >> > Liam: I'm not sure what you prefer for the MAINTAINERS entry, so let me >> > know if you want anything changed. There are also a few other options, >> > for example, I could just add the files under the existing MAPLE TREE >> > entry? The get_maintainers script should still send any relevant patches >> > my way because they also match the RUST entry that has a wildcard on the >> > rust/ directory. >> >> From v1 [1]: >> >> >> We should have another section for the maple tree, since it's not just >> >> used for mm. Your stated plan is to use it for GPU allocations and the >> >> code doesn't live in mm/, wdyt? >> >> > Sure, I can add a new section if you prefer that. >> >> Maple tree is already used outside of mm, e.g. for regmap stuff and I also use >> it in nouveau. Hence, I read this as moving maple tree to e.g. lib/ adjusting >> the existing entry. >> >> I personally think that - of course unless the affected people prefer otherwise >> - it is usually best to keep a single maintainers entry for the C and the Rust >> code. Maybe Alice can simply be added to the existing maintainers entry? >> >> What do you think? > > I'm not sure what you mean by lib/ since the lib files are spread into > other entries by the looks of it? I think I misunderstood your comment from [1] above, and, despite knowing better, mistakenly assumed otherwise -- just ignore this comment. > I'm okay with the entry below or adjusting the existing one. If you're both fine with either, I suggest to keep a single entry for both. In general I think it's better if we try to avoid to differentiate between Rust and C code of a single subsystem (or component) maintenance wise unless there are specific reasons. Even though sometimes it's just a formality, I think it can help to bring people together and learn from each other. There more good examples we can set up for this, the better. :) >> [1] https://lore.kernel.org/all/aJW3L3SEVUl_AVvN@google.com/
On Tue, Aug 19, 2025 at 01:49:27PM +0200, Danilo Krummrich wrote: > On Tue Aug 19, 2025 at 12:34 PM CEST, Alice Ryhl wrote: > > Similar to and just below the existing MAPLE TREE entry. > > > > Signed-off-by: Alice Ryhl <aliceryhl@google.com> > > --- > > Liam: I'm not sure what you prefer for the MAINTAINERS entry, so let me > > know if you want anything changed. There are also a few other options, > > for example, I could just add the files under the existing MAPLE TREE > > entry? The get_maintainers script should still send any relevant patches > > my way because they also match the RUST entry that has a wildcard on the > > rust/ directory. > > From v1 [1]: > > >> We should have another section for the maple tree, since it's not just > >> used for mm. Your stated plan is to use it for GPU allocations and the > >> code doesn't live in mm/, wdyt? > > > Sure, I can add a new section if you prefer that. > > Maple tree is already used outside of mm, e.g. for regmap stuff and I also use > it in nouveau. Hence, I read this as moving maple tree to e.g. lib/ adjusting > the existing entry. It's already in lib/ ? > I personally think that - of course unless the affected people prefer otherwise > - it is usually best to keep a single maintainers entry for the C and the Rust > code. Maybe Alice can simply be added to the existing maintainers entry? > > What do you think? That works for me too. Alice
© 2016 - 2025 Red Hat, Inc.