From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/10115] Regression with inet_sock @cast from 0.9 to 0.9.7 on 2.6.9 kernel
Date: Wed, 06 May 2009 10:19:00 -0000 [thread overview]
Message-ID: <20090506101853.12107.qmail@sourceware.org> (raw)
In-Reply-To: <20090429163815.10115.nuhn@physik.rwth-aachen.de>
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|Problems |Regression with inet_sock
| |@cast from 0.9 to 0.9.7 on
| |2.6.9 kernel
http://sourceware.org/bugzilla/show_bug.cgi?id=10115
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-05-06 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 16:38 [Bug tapsets/10115] New: Problems nuhn at physik dot rwth-aachen dot de
2009-05-06 10:19 ` mjw at redhat dot com [this message]
2009-11-18 19:21 ` [Bug tapsets/10115] Regression with inet_sock @cast from 0.9 to 0.9.7 on 2.6.9 kernel dsmith at redhat dot com
2010-04-19 14:14 ` fche at redhat dot com
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=20090506101853.12107.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).