From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
"linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: [ANNOUNCE] trace-cmd v2.8.1
Date: Fri, 5 Jul 2019 12:34:11 -0400 [thread overview]
Message-ID: <20190705123411.4285e625@gandalf.local.home> (raw)
Just after releasing 2.8, some bugs were found (isn't that always the
case?). Now we have 2.8.1 stable release:
http://trace-cmd.org
-- Steve
Short log here:
Greg Thelen (2):
trace-cmd: Always initialize write_record() len
trace-cmd: Avoid using uninitialized handle
Steven Rostedt (VMware) (1):
trace-cmd: Version 2.8.1
Tzvetomir Stoyanov (VMware) (1):
trace-cmd: Do not free pages from the lookup table in struct cpu_data in case trace file is loaded.
next reply other threads:[~2019-07-05 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 16:34 Steven Rostedt [this message]
2019-07-05 21:20 ` [ANNOUNCE] trace-cmd v2.8.1 Bhaskar Chowdhury
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=20190705123411.4285e625@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.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 NNTP newsgroup(s).