From: Camila Alvarez <cam.alvarez.i@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Submitting a selftest patch
Date: Tue, 7 May 2024 22:38:20 -0400 [thread overview]
Message-ID: <CAEgcBZgSSJ9K+-Sj-p+YY1NXxsr81XmjUWm98g-dig6NDUo_KQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 340 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 462 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2024-05-08 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 2:38 Camila Alvarez [this message]
2024-05-08 16:21 ` Submitting a selftest patch Jules Irenge
2024-05-08 16:35 ` Siddh Raman Pant
2024-05-08 16:49 ` Tom Mitchell
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=CAEgcBZgSSJ9K+-Sj-p+YY1NXxsr81XmjUWm98g-dig6NDUo_KQ@mail.gmail.com \
--to=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).