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-1.2-100-gd2e3581
Date: Thu, 29 Apr 2010 18:01:00 -0000	[thread overview]
Message-ID: <20100429180116.13988.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  d2e358156629530012bab02ba6d2d21d4c494263 (commit)
      from  2b85828e4e49ea29276714013ce1c1ef6207214c (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 d2e358156629530012bab02ba6d2d21d4c494263
Author: David Smith <dsmith@redhat.com>
Date:   Thu Apr 29 12:58:01 2010 -0500

    Get memory.stp embedded-C functions working on 2.6.9 kernels (RHEL4).
    
    * tapset/memory.stp: Define __GFP_DMA32, GFP_DMA32, __GFP_ZERO,
      __GFP_NOMEMALLOC, and __GFP_HARDWALL if not defined.
    * testsuite/buildok/memory-embedded.stp: New testcase.

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

Summary of changes:
 tapset/memory.stp                     |   20 ++++++++++++++++++++
 testsuite/buildok/memory-embedded.stp |    8 ++++++++
 2 files changed, 28 insertions(+), 0 deletions(-)
 create mode 100755 testsuite/buildok/memory-embedded.stp


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


                 reply	other threads:[~2010-04-29 18:01 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=20100429180116.13988.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).