From: CRISTIAN ANDRES VARGAS GONZALEZ <vargascristian@americana.edu.co>
To: kernelnewbies@kernelnewbies.org
Subject: Test the kernel code
Date: Fri, 4 Oct 2019 22:07:21 -0500 [thread overview]
Message-ID: <CABfRCzh5=ah=JKZYXFdVGzpfWsJagodVKLNm4wKrDij-ocPgyw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 254 bytes --]
Hello
I am starting to develop the kernel and I have been compiling the kernel,
now it has been compiling for some time now. When a patch is added, should
everything be compiled again? Or is there a different way to test the code
that has been written?
[-- Attachment #1.2: Type: text/html, Size: 447 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:[~2019-10-05 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 3:07 CRISTIAN ANDRES VARGAS GONZALEZ [this message]
2019-10-05 3:52 ` Test the kernel code Adam Zerella
2019-10-05 4:18 ` Valdis Klētnieks
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='CABfRCzh5=ah=JKZYXFdVGzpfWsJagodVKLNm4wKrDij-ocPgyw@mail.gmail.com' \
--to=vargascristian@americana.edu.co \
--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 NNTP newsgroup(s).