From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: the Linux kernel, testsuites, and maybe *you*
Date: Fri, 31 Aug 2007 17:22:19 -0400 [thread overview]
Message-ID: <8bd0f97a0708311422u309ff09cs24dfe64ff535a982@mail.gmail.com> (raw)
is there any sort of standard for testing and integration into
mainline ? in the Blackfin world, we've been developing little
external kernel modules and adding them to our own testsuite, but
often times these things are not Blackfin specific. case in point,
we're integrating a string testsuite to make sure all of the fun str*
and mem* functions are sane and operate as they expected, but rather
than having just Blackfin benefit here, i'd like to see this pushed
upstream ...
i'm fully aware of LTP (as i work on it), but i feel that serves a
great purpose for exercising the API/ABI exposed to userspace either
directly through the kernel or indirectly through the system libc ...
it isnt a very good tool for testing kernel internals, especially as
the kernel changes and evolves.
is there a framework already in place i'm not aware of ? should there
be ? should this all live in LTP ? i wouldnt mind an option under
kernel hacking "Enable testsuites" ... as far as i can tell, the
testing process is really based extensively on feedback from people,
nothing really automated.
-mike
next reply other threads:[~2007-08-31 21:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 21:22 Mike Frysinger [this message]
2007-09-01 6:14 ` Robin Getz
2007-09-01 22:52 ` Mike Frysinger
2007-09-01 22:08 ` Andi Kleen
2007-09-01 22:50 ` Mike Frysinger
2007-09-02 6:59 ` Andi Kleen
2007-09-02 15:15 ` Mike Frysinger
2007-09-02 15:43 ` Andi Kleen
2007-09-04 15:05 ` Mike Frysinger
2007-09-05 17:51 ` Mike Frysinger
2007-09-02 18:20 ` Håvard Skinnemoen
2007-09-04 14:41 ` Robin Getz
2007-09-02 2:34 ` Bill Davidsen
2007-09-02 3:44 ` Mike Frysinger
2007-09-03 13:37 ` Bill Davidsen
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=8bd0f97a0708311422u309ff09cs24dfe64ff535a982@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome