From: Tom Mitchell <niftylinkern@niftyegg.com>
To: Camila Alvarez <cam.alvarez.i@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Submitting a selftest patch
Date: Wed, 8 May 2024 09:49:37 -0700 [thread overview]
Message-ID: <CAAMy4UTJ22V1T9jWwoH6O2t0H+0+4kh-VKc8a_mOfGXOdNHXbQ@mail.gmail.com> (raw)
In-Reply-To: <CAEgcBZgSSJ9K+-Sj-p+YY1NXxsr81XmjUWm98g-dig6NDUo_KQ@mail.gmail.com>
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
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2024-05-08 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 2:38 Submitting a selftest patch Camila Alvarez
2024-05-08 16:21 ` Jules Irenge
2024-05-08 16:35 ` Siddh Raman Pant
2024-05-08 16:49 ` Tom Mitchell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAMy4UTJ22V1T9jWwoH6O2t0H+0+4kh-VKc8a_mOfGXOdNHXbQ@mail.gmail.com \
--to=niftylinkern@niftyegg.com \
--cc=cam.alvarez.i@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).