From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How do you test Linux kernel?
Date: Wed, 20 Jul 2016 09:39:52 -0700 [thread overview]
Message-ID: <20160720163952.GA14809@kroah.com> (raw)
In-Reply-To: <20160720141927.2615cc23@fujitsu>
On Wed, Jul 20, 2016 at 02:19:27PM +0300, Aleksander Alekseev wrote:
> Hello
>
> It is my understanding that Linux kernel doesn't has usual `make check`
> or `make test` command.
It doesn't? Have you checked?
$ make help | grep test
Kernel selftest
kselftest - Build and run kernel selftest (run as root)
running kselftest on it
kselftest-clean - Remove all generated kselftest files
kselftest-merge - Merge all the config dependencies of kselftest to existed
> There are LTP [1] and other related projects
> instead. Could you tell me please what test suits (if any) do _you_ run
> in practice?
It depends on what changes you make, to determine how you test it.
thanks,
greg k-h
next prev parent reply other threads:[~2016-07-20 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 11:19 How do you test Linux kernel? Aleksander Alekseev
2016-07-20 16:39 ` Greg KH [this message]
2016-07-20 22:50 ` [SPAM] " Bernd Petrovitsch
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=20160720163952.GA14809@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.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).