public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: dsmith@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.8-191-g0a93473
Date: Wed, 22 Jul 2009 19:55:00 -0000	[thread overview]
Message-ID: <20090722195526.31986.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  0a9347310bfd77fc3e353a75f5abee242da0f977 (commit)
      from  d51df7d73716deb8fc99877a37a3043a70cf613e (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 0a9347310bfd77fc3e353a75f5abee242da0f977
Author: David Smith <dsmith@redhat.com>
Date:   Wed Jul 22 14:42:18 2009 -0500

    Make ring_buffer transport work on new kernels.
    * runtime/transport/ring_buffer.c (_stp_event_to_user): Added debug prints.
      (_stp_ring_buffer_consume): New function.
      (_stp_find_next_event): Avoid incrementing the buffer iterator here.
      (_stp_data_write_commit): Added debug prints.

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

Summary of changes:
 runtime/transport/ring_buffer.c |   57 ++++++++++++++++++++++++++++++---------
 1 files changed, 44 insertions(+), 13 deletions(-)


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


                 reply	other threads:[~2009-07-22 19:55 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=20090722195526.31986.qmail@sourceware.org \
    --to=dsmith@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).