From: libin@sgepri.sgcc.com.cn (libin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernelnewbies Digest, Vol 49, Issue 7
Date: Thu, 4 Dec 2014 11:21:44 +0800 [thread overview]
Message-ID: <201412041121440556236@sgepri.sgcc.com.cn> (raw)
In-Reply-To: mailman.1.1417626001.14626.kernelnewbies@kernelnewbies.org
hello?
Does anybody know what test should do before a patch added into the kernel ?
I am interested in the method to prove the stability and performance of kernel , especially the stability .
can anybody help me ?
thanks very much !
icelee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20141204/12f1ba52/attachment.html
next parent reply other threads:[~2014-12-04 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1417626001.14626.kernelnewbies@kernelnewbies.org>
2014-12-04 3:21 ` libin [this message]
2014-12-04 3:35 ` Kernelnewbies Digest, Vol 49, Issue 7 Saket Sinha
2014-12-04 3:37 ` stability ? libin
2014-12-04 7:27 ` libin
2014-12-04 10:36 ` Greg Freemyer
2014-12-04 15:02 ` Valdis.Kletnieks at vt.edu
2014-12-04 16:02 ` nick
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=201412041121440556236@sgepri.sgcc.com.cn \
--to=libin@sgepri.sgcc.com.cn \
--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).