public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: hunt@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: src/runtime/staprun ChangeLog mainloop.c relay ...
Date: Sun, 18 Mar 2007 18:19:00 -0000 [thread overview]
Message-ID: <20070318181927.18311.qmail@sourceware.org> (raw)
CVSROOT: /cvs/systemtap
Module name: src
Changes by: hunt@sourceware.org 2007-03-18 18:19:27
Modified files:
runtime/staprun: ChangeLog mainloop.c relay.c relay_old.c
staprun.h
Removed files:
runtime/staprun: ChangeLog~ stp_merge.c~
Log message:
2007-03-18 Martin Hunt <hunt@redhat.com>
* staprun.h (VERSION_CMD): Command to use for version check.
Changes to support runtime decision on new or old transport.
* mainloop.c (init_staprun): Check the kernel version at runtime
instead of at compile time.
(cleanup_and_exit): Call the correct relayfs close function.
(stp_main_loop): Call the correct relayfs init function.
* relay.c: Remove ifdef wrapper. File is always compiled and used
if the kernel version is appropriate.
* relay_old.c: Ditto.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/staprun/ChangeLog.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/staprun/mainloop.c.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/staprun/relay.c.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/staprun/relay_old.c.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/staprun/staprun.h.diff?cvsroot=systemtap&r1=1.1&r2=1.2
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/staprun/ChangeLog~.diff?cvsroot=systemtap&r1=1.1&r2=NONE
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/staprun/stp_merge.c~.diff?cvsroot=systemtap&r1=1.1&r2=NONE
reply other threads:[~2007-03-18 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070318181927.18311.qmail@sourceware.org \
--to=hunt@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).