From: "Randy.Dunlap" <firstname.lastname@example.org>
To: george anzinger <email@example.com>
Cc: John Levon <firstname.lastname@example.org>,
Subject: Re: [PATCH 6/6] High-res-timers part 6 (support-man) take 2
Date: Mon, 30 Sep 2002 14:21:10 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33L2.email@example.com> (raw)
On Mon, 30 Sep 2002, george anzinger wrote:
| "Randy.Dunlap" wrote:
| > On Sat, 28 Sep 2002, John Levon wrote:
| > | On Sat, Sep 28, 2002 at 10:32:08AM -0700, george anzinger wrote:
| > |
| > | > The 4th, 5th, and 6th parts are support code and not really
| > | > part of the kernel.
| > |
| > | So ...
| > |
| > | > This part contains man pages for the new system calls.
| > |
| > | ... why are they here ?
| > |
| > | http://freshmeat.net/projects/man-pages/
| > I agree, please let's not clutter the kernel tree.
| Oh, I agree also. I don't think any of the high-res-timers
| support patches belong in the tree. For testing and
| verifying the system calls, however, it is nice to have
| them. It is easy to do the patch and then move the whole
| directory as this is the only thing in it.
| I might suggest, however, that we should have a regression
| test set for the kernel "somewhere". Does such a thing
| exist? I haven't seen it, but then I have yet to see a
| great number of things ;)
I believe that IBM's LTP project does regression testing on
2.5.x kernels. That's more for things like compile/build and
syscall correctness IIRC. Not so much as performance (regression)
next prev parent reply other threads:[~2002-09-30 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 17:32 [PATCH 6/6] High-res-timers part 6 (support-man) take 2 george anzinger
2002-09-28 18:20 ` John Levon
2002-09-28 19:14 ` george anzinger
2002-09-30 18:14 ` Randy.Dunlap
2002-09-30 21:15 ` george anzinger
2002-09-30 21:21 ` Randy.Dunlap [this message]
2002-09-30 23:27 ` John Levon
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).