From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/25265] tapscripts using ustack, ubacktrace etc fail to compile on kernel 5.3
Date: Sun, 29 Dec 2019 19:53:00 -0000 [thread overview]
Message-ID: <bug-25265-6586-UHoInvYWG5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25265-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25265
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |fche at redhat dot com
Resolution|--- |FIXED
--- Comment #6 from Frank Ch. Eigler <fche at redhat dot com> ---
thanks, merged!
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2019-12-29 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 5:42 [Bug runtime/25265] New: tapscripts using ustack, ubacktrace etc fail to compile on kernel 3.4 craig.ringer at 2ndquadrant dot com
2019-12-10 6:05 ` [Bug runtime/25265] " craig.ringer at 2ndquadrant dot com
2019-12-10 6:12 ` craig.ringer at 2ndquadrant dot com
2019-12-10 6:23 ` craig.ringer at 2ndquadrant dot com
2019-12-10 6:34 ` craig.ringer at 2ndquadrant dot com
2019-12-10 6:51 ` [Bug runtime/25265] tapscripts using ustack, ubacktrace etc fail to compile on kernel 5.3 craig.ringer at 2ndquadrant dot com
2019-12-10 6:51 ` [Bug runtime/25265] tapscripts using ustack, ubacktrace etc fail to compile on kernel 3.4 craig.ringer at 2ndquadrant dot com
2019-12-29 5:33 ` [Bug runtime/25265] tapscripts using ustack, ubacktrace etc fail to compile on kernel 5.3 craig.ringer at 2ndquadrant dot com
2019-12-29 19:53 ` fche 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=bug-25265-6586-UHoInvYWG5@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@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: 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).