From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/18320] ring_buffer.exp error: implicit declaration of function '__get_cpu_var'
Date: Wed, 06 Dec 2023 20:28:53 +0000 [thread overview]
Message-ID: <bug-18320-6586-yem8PPT99E@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18320-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18320
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
This code containing __get_cpu_var() reference was removed by git commit
81a7b6f53fc0ddf4203a66637a42bfe715bb1025
Author: Frank Ch. Eigler <fche@redhat.com> 2020-09-14 19:54:04
Committer: Frank Ch. Eigler <fche@redhat.com> 2020-09-17 10:56:25
Parent: 5b701f181c4e5d8fffc067258ab2f6d771e88255 (Update
emacs/systemtap-mode.el for emacs 27)
Child: 4c5bed543b9b8c4b9cc544762afc9810938f88fa (Fix get_user_pages{,_remote}
for 5.9 kernels.)
Branches: master, remotes/origin/master and many more (41)
Follows: release-4.3
Precedes: release-4.4
deprecate STP_TRANSPORT_VERSION=3 (ring_buffer)
The non-default ring_buffer transport hasn't even compiled in some
time, and appears to have no compelling reason to keep the code
around. Let's remove the code.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2023-12-06 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 14:28 [Bug runtime/18320] New: " mcermak at redhat dot com
2015-12-08 16:00 ` [Bug runtime/18320] " wcohen at redhat dot com
2023-12-06 20:28 ` wcohen 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-18320-6586-yem8PPT99E@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).