[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251109113741.102337-1-swarajgaikwad1925@gmail.com>
Date: Sun, 9 Nov 2025 11:37:38 +0000
From: Swaraj Gaikwad <swarajgaikwad1925@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
linux-mm@...ck.org (open list:MEMORY MANAGEMENT),
linux-kernel@...r.kernel.org (open list)
Cc: Swaraj Gaikwad <swarajgaikwad1925@...il.com>
Subject: [RFC] Guidance on contributing to the MM subsystem and finding tasks
Hi all,
I’ve been following the MM subsystem for a while and have submitted a few
small patches (mostly cleanups and basic fixes).I’d really like to become
more involved and contribute to meaningful memory management work, but I’m
having some trouble figuring out how to identify useful areas to work on.
I have also looked at some TODOs in the mm/ code and submitted a patch for
one of them. I’ve tried looking into syzbot reports as well, but often by
the time I finish understanding the issue, someone else has already sent a
fix. I’d still like to learn from such debugging efforts, but it would be
great to find areas where I can make steady progress and contribute patches
that are actually helpful.
Could someone please share some guidance or suggestions on:
- How to find open problems or areas that need help in MM?
- Any advice for someone trying to move from small fixes toward more
substantial contributions?
- And if possible, could you suggest a few small or medium tasks that are
suitable for new contributors to the MM subsystem, the kind of things that
would be genuinely helpful and likely to be accepted?
I’d really appreciate any pointers or direction.
Thanks for your time and for maintaining this amazing subsystem.
Best regards,
Swaraj Gaikwad <swarajgaikwad1925@...il.com>
Signed-off-by: Swaraj Gaikwad <swarajgaikwad1925@...il.com>
Powered by blists - more mailing lists