From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/28079] adapt to kernel 5.14 task_struct.__state change
Date: Tue, 20 Jul 2021 16:03:39 +0000 [thread overview]
Message-ID: <bug-28079-6586-ILD1Sv4Vi7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28079-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28079
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cxxtao at gmail dot com
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
*** Bug 28107 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-07-20 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 15:09 [Bug runtime/28079] New: " scox at redhat dot com
2021-07-13 14:55 ` [Bug runtime/28079] " scox at redhat dot com
2021-07-20 16:03 ` wcohen at redhat dot com [this message]
2021-08-19 17:59 ` scox 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-28079-6586-ILD1Sv4Vi7@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).