From: "scox at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/27728] at_*.exp regressions (from bunsen data)
Date: Wed, 25 May 2022 15:58:19 +0000 [thread overview]
Message-ID: <bug-27728-6586-NtZnxnkj3Y@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27728-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27728
Stan Cox <scox at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |scox at redhat dot com
Resolution|--- |FIXED
--- Comment #3 from Stan Cox <scox at redhat dot com> ---
73ae70cfc Fix at_deref and at_var_cu test driver issues
531e708c8 Use explicit @var kernel module for at_var_tracepoint test
5e12c0e21 Probe do_utimes for handling utimes call
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-05-25 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 20:49 [Bug runtime/27728] New: " me at serhei dot io
2021-04-14 18:35 ` [Bug runtime/27728] " me at serhei dot io
2021-04-14 20:06 ` me at serhei dot io
2022-05-25 15:58 ` scox 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-27728-6586-NtZnxnkj3Y@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).