From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/4553] i686 RHEL4u5 systemcall tapset argument issues with 2.6.9-55.ELsmp kernel
Date: Thu, 14 Jan 2010 17:03:00 -0000 [thread overview]
Message-ID: <20100114170309.23547.qmail@sourceware.org> (raw)
In-Reply-To: <20070525215356.4553.wcohen@redhat.com>
------- Additional Comments From dsmith at redhat dot com 2010-01-14 17:03 -------
On current rhel5 kernels (2.6.18-164.9.1.el5) we don't see this problem, so I'm
closing this as WONTFIX.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |dsmith at redhat dot com
Status|ASSIGNED |RESOLVED
Resolution| |WONTFIX
http://sourceware.org/bugzilla/show_bug.cgi?id=4553
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2010-01-14 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 21:54 [Bug tapsets/4553] New: " wcohen at redhat dot com
2007-06-07 16:29 ` [Bug tapsets/4553] " wcohen at redhat dot com
2007-06-07 21:01 ` dsmith at redhat dot com
2007-06-08 18:14 ` dsmith at redhat dot com
2010-01-14 17:03 ` 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=20100114170309.23547.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).