From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/11599] Support data pointer in tracepoint callbacks
Date: Fri, 22 May 2020 20:50:40 +0000 [thread overview]
Message-ID: <bug-11599-6586-EUHObKfxe3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11599-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=11599
Serhei Makarov <me at serhei dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |me at serhei dot io
--- Comment #3 from Serhei Makarov <me at serhei dot io> ---
Commits e17cf7003724+a8ebb9d338e8 update STAPCONF_TRACEPOINT_HAS_DATA to work
with kernel 5.7.0+ which removes DECLARE_TRACE_NOARGS.
--
You are receiving this mail because:
You are the assignee for the bug.
next parent reply other threads:[~2020-05-22 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11599-6586@http.sourceware.org/bugzilla/>
2020-05-22 20:50 ` me at serhei dot io [this message]
2010-05-14 19:16 [Bug tapsets/11599] New: " jistone at redhat dot com
2010-06-01 18:23 ` [Bug tapsets/11599] " jistone at redhat dot com
2010-06-02 22:45 ` jistone 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=bug-11599-6586-EUHObKfxe3@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).