public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-106-g1312868 Date: Mon, 12 Mar 2012 22:07:00 -0000 [thread overview] Message-ID: <20120312220729.26538.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via 1312868434fee61eb14d6e3e4aff12a5f1f2647f (commit) from 43cb3d7fc1f8b423f716e138d041c073917f50ed (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 1312868434fee61eb14d6e3e4aff12a5f1f2647f Author: Josh Stone <jistone@redhat.com> Date: Mon Mar 12 14:42:28 2012 -0700 Adapt to the inode-uprobes name change in tip We now have the functions register_uprobe -> uprobe_register and unregister_uprobe -> uprobe_unregister. The client API has otherwise not changed. I've made our code reflect the new names as much as possible, treating the old names as the exceptional case, in case we ever want to remove that compatibility. For now, it should work in all cases, although I don't have a full complement of old/new & exported/!exported kernels to test with. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 23 ++++++++++++++++++++--- runtime/autoconf-old-inode-uprobes.c | 12 ++++++++++++ runtime/runtime.h | 8 ++++---- runtime/transport/transport.c | 22 ++++++++++++++-------- runtime/uprobes-inode.c | 20 ++++++++++++-------- 5 files changed, 62 insertions(+), 23 deletions(-) create mode 100644 runtime/autoconf-old-inode-uprobes.c hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-03-12 22:07 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=20120312220729.26538.qmail@sourceware.org \ --to=jistone@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@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: linkBe 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).