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.7-142-gf1410a8 Date: Wed, 04 Apr 2012 20:51:00 -0000 [thread overview] Message-ID: <20120404205111.1154.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 f1410a8a2a9ad5670aa727339062f1921e122a27 (commit) from 414b89b8a3573760d6aa05c41555447c17484ea2 (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 f1410a8a2a9ad5670aa727339062f1921e122a27 Author: David Smith <dsmith@redhat.com> Date: Wed Apr 4 15:50:29 2012 -0500 Fix module build problem on ARM. * runtime/vma.c (_stp_vma_match_vdso): Call __access_process_vm_noflush() instead of __access_process_vm(). When reading user memory, the __access_process_vm_noflush() and __access_process_vm() functions are fairly equivalent and we're only reading here. (The write side of __access_process_vm() calls non-exported functions on ia64, mips, and arm.) * runtime/sym.c (_stp_build_id_check): Ditto. ----------------------------------------------------------------------- Summary of changes: runtime/sym.c | 13 +++++-------- runtime/vma.c | 14 +++++--------- 2 files changed, 10 insertions(+), 17 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-04-04 20:51 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=20120404205111.1154.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: 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).