public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: wcohen@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-599-g2a389af
Date: Thu, 15 Dec 2011 16:31:00 -0000	[thread overview]
Message-ID: <20111215163129.26056.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  2a389af7f86a779a360ab0e2bcd71c3093e79dcf (commit)
      from  2cf251473fcdde2cdc2d74a5ef6240478383337c (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 2a389af7f86a779a360ab0e2bcd71c3093e79dcf
Author: William Cohen <wcohen@redhat.com>
Date:   Thu Dec 15 11:27:45 2011 -0500

    Adjust periodic.stp example to run on kernels without struct delayed_work
    
    RHEL-5 kernels have the timer_expire_entry tracepoint, but do not have
    struct delayed_work.  Some @defined magic is used to select the
    fallback if struct delayed_work is not around.

-----------------------------------------------------------------------

Summary of changes:
 .../systemtap.examples/profiling/periodic.stp      |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2011-12-15 16:31 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=20111215163129.26056.qmail@sourceware.org \
    --to=wcohen@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: 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).