From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/6969] syscall tapset broken on s390x
Date: Fri, 31 Oct 2008 14:04:00 -0000 [thread overview]
Message-ID: <20081031140321.6791.qmail@sourceware.org> (raw)
In-Reply-To: <20081020200858.6969.dsmith@redhat.com>
------- Additional Comments From dsmith at redhat dot com 2008-10-31 14:03 -------
> Please retest on s390x.
I've tested this on s390x, and it seems to work fine.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
http://sourceware.org/bugzilla/show_bug.cgi?id=6969
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2008-10-31 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 20:10 [Bug tapsets/6969] New: " dsmith at redhat dot com
2008-10-20 21:02 ` [Bug tapsets/6969] " jkenisto at us dot ibm dot com
2008-10-23 7:36 ` mjw at redhat dot com
2008-10-23 18:43 ` mjw at redhat dot com
2008-10-31 14:04 ` dsmith at redhat dot com [this message]
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=20081031140321.6791.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).