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-0.7-388-gf7674e5 Date: Fri, 24 Oct 2008 19:33:00 -0000 [thread overview] Message-ID: <20081024193324.13601.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 f7674e54ccb92a1b99af6e930bab75560ff2dfd7 (commit) from 2237d27b8146dd25a65e833a5117318c7502a5e9 (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 f7674e54ccb92a1b99af6e930bab75560ff2dfd7 Author: Josh Stone <joshua.i.stone@intel.com> Date: Fri Oct 24 12:32:36 2008 -0700 Fix hrtimer.expires name change. The field is renamed to _expires starting in 2.6.28-rc1, and it's not meant to be directly manipulated. Instead hrtimer users are supposed to use hrtimer_get_expires and hrtimer_set_expires. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 8 ++++++++ buildrun.cxx | 1 + runtime/ChangeLog | 4 ++++ runtime/autoconf-hrtimer-getset-expires.c | 6 ++++++ tapsets.cxx | 11 ++++++++--- 5 files changed, 27 insertions(+), 3 deletions(-) create mode 100644 runtime/autoconf-hrtimer-getset-expires.c hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2008-10-24 19:33 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=20081024193324.13601.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).