From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
John Kacur <jkacur@redhat.com>, Wan Jiabing <wanjiabing@vivo.com>
Subject: [GIT PULL] tracing tools: Updates for 5.19
Date: Sun, 29 May 2022 13:09:17 -0400 [thread overview]
Message-ID: <20220529130917.06df783b@rorschach.local.home> (raw)
Linus,
[ You did tell me that you prefer the tools to be a separate pull
request than the kernel changes.]
Updates to Real Time Linux Analysis tool for 5.19:
Various clean ups and fixes.
Please pull the latest trace-tools-v5.19 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-tools-v5.19
Tag SHA1: 70796e161d97186eb56dd830a504d3ab154b283d
Head SHA1: dada03db9bb1984826e61cfcf1418ac73848324d
Daniel Bristot de Oliveira (3):
rtla/Makefile: Properly handle dependencies
rtla: Fix __set_sched_attr error message
rtla: Remove procps-ng dependency
John Kacur (2):
rtla: Don't overwrite existing directory mode
rtla: Minor grammar fix for rtla README
Wan Jiabing (1):
rtla: Avoid record NULL pointer dereference
----
Documentation/tools/rtla/Makefile | 14 ++++-
tools/tracing/rtla/Makefile | 40 +++++++++++-
tools/tracing/rtla/README.txt | 13 ++--
tools/tracing/rtla/src/osnoise_hist.c | 5 +-
tools/tracing/rtla/src/osnoise_top.c | 9 +--
tools/tracing/rtla/src/timerlat_hist.c | 11 ++--
tools/tracing/rtla/src/timerlat_top.c | 11 ++--
tools/tracing/rtla/src/utils.c | 108 ++++++++++++++++++++++++++-------
tools/tracing/rtla/src/utils.h | 3 +-
9 files changed, 164 insertions(+), 50 deletions(-)
---------------------------
next reply other threads:[~2022-05-29 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 17:09 Steven Rostedt [this message]
2022-05-29 17:59 ` pr-tracker-bot
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=20220529130917.06df783b@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wanjiabing@vivo.com \
/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
all inboxes | Powered by JetHome®