It's very easy for Linux kernel driver maintainers to build strongholds around their code, as it's very difficult for the lay contributor to understand unusual macros or code that's often not properly documented and assumed to be only edited by "experts". As this is often the case with DRM drivers, we propose the adoption of KUnit as a tool not only for making such code more reliable, but also for making it more approachable as unit tests provide a simple and elegant way of finding exactly which piece of code has been broken. We explore this magic tool's adoption in the context of AMD's jarring DML submodule and how we can turn it from a spooky piece of code to a more friendly face.
|Code of Conduct||Yes|
|GSoC, EVoC or Outreachy||Yes|
|For which conference do you send the proposal?||X.Org Developers Conference 2022|
|In-person or virtual presentation||In-person|