That 's cool. I would send a patch then a selftest separately but could ask the maintainer. Jules Irenge Open source contributor: https://bit.ly/40GblaQ Blog: https:// <https://www.strava.com/athletes/72390635> www.julesirenge.blog twitter: @jules_irenge strava: https://www.strava.com/athletes/72390635 linkedIn: *https://www.linkedin.com/in/jules-irenge-87282238/ <https://www.linkedin.com/in/jules-irenge-87282238/>* On Wed, 8 May 2024 at 03:39, Camila Alvarez <cam.alvarez.i@gmail.com> wrote:

I’ve been discussing a bug with one of the maintainers of a subsystem. At one point I was asked to craft a selftest for the issue.

My question is: how do I send the patch with the selftest? Do I need to reference the email where the selftest request was made? Or should I just send it as an independent patch?

Thanks in advance _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Ask the maintainers! In an ideal world there would be a directory or package of self tests associated with the subsystem. Alternatively: If you have an account on git make a "My work is GPL3" statement file then clone or fork and add your patch and add the self test. A personal fork gives you a playground, you can merge it back or just flush. https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html On Tue, May 7, 2024 at 7:39 PM Camila Alvarez <cam.alvarez.i@gmail.com> wrote:

I’ve been discussing a bug with one of the maintainers of a subsystem. At one point I was asked to craft a selftest for the issue.

My question is: how do I send the patch with the selftest? Do I need to reference the email where the selftest request was made? Or should I just send it as an independent patch?

Thanks in advance _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies