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.7-408-gd4b35e9 Date: Tue, 28 Oct 2008 19:34:00 -0000 [thread overview] Message-ID: <20081028193441.22388.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 d4b35e96eab28e96353b53954111662cf76ced2d (commit) from 2f6db74ede1d91c5db9c08c6f0dd1056a6992817 (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 d4b35e96eab28e96353b53954111662cf76ced2d Author: David Smith <dsmith@redhat.com> Date: Tue Oct 28 14:34:28 2008 -0500 PR6972. Fixed vfs tapset. 2008-10-28 David Smith <dsmith@redhat.com> PR6972 * vfs.stp (generic.fop.aio_read): Works under 2.6.18 kernels, such as RHEL5. (generic.fop.aio_read.return): Ditto. (vfs.__set_page_dirty_buffers): Fixed small bug. (_vfs.block_write_begin): Only use for kernels >= 2.6.24. (_vfs.block_write_begin.return): Ditto. (_vfs.block_write_end): Ditto. (_vfs.block_write_end.return): Ditto. 2008-10-28 David Smith <dsmith@redhat.com> * buildok/vfs_testcase.stp: Fixes for updated vfs tapset. ----------------------------------------------------------------------- Summary of changes: tapset/ChangeLog | 12 ++++++++++++ tapset/vfs.stp | 30 +++++++++++++++++++++--------- testsuite/ChangeLog | 4 ++++ testsuite/buildok/vfs_testcase.stp | 7 +++---- 4 files changed, 40 insertions(+), 13 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2008-10-28 19:34 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=20081028193441.22388.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).