public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: src/testsuite ChangeLog buildok/aux_syscalls-e ...
Date: Mon, 24 Sep 2007 17:52:00 -0000 [thread overview]
Message-ID: <20070924175241.28027.qmail@sourceware.org> (raw)
CVSROOT: /cvs/systemtap
Module name: src
Changes by: fche@sourceware.org 2007-09-24 17:52:41
Modified files:
testsuite : ChangeLog
Added files:
testsuite/buildok: aux_syscalls-embedded.stp
conversions-embedded.stp
inet_sock-embedded.stp ioblock-embedded.stp
ioscheduler-embedded.stp nfs-embedded.stp
nfs_proc-embedded.stp nfsd-embedded.stp
rpc-embedded.stp scsi-embedded.stp
signal-embedded.stp socket-embedded.stp
task-embedded.stp tcp-embedded.stp
vfs-embedded.stp
Log message:
* buildok test cases for every embedded-C function
2007-09-24 Frank Ch. Eigler <fche@elastic.org>
* buildok/*-embedded.stp: New test case for every embedded-C
function in the tapsets.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/ChangeLog.diff?cvsroot=systemtap&r1=1.155&r2=1.156
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/aux_syscalls-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/conversions-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/inet_sock-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/ioblock-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/ioscheduler-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/nfs-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/nfs_proc-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/nfsd-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/rpc-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/scsi-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/signal-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/socket-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/task-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/tcp-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/vfs-embedded.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
next reply other threads:[~2007-09-24 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 17:52 fche [this message]
2007-10-05 17:48 hunt
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=20070924175241.28027.qmail@sourceware.org \
--to=fche@sourceware.org \
--cc=systemtap-cvs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).