From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] rtla: v5.18-rc2 Fixes
Date: Tue, 19 Apr 2022 18:23:25 +0200 [thread overview]
Message-ID: <d63d91c6-a466-0ca1-9d0d-76ad37f9eff9@kernel.org> (raw)
In-Reply-To: <cover.1650029027.git.bristot@kernel.org>
Steven,
Please ignore this email thread. For some reason I do not know, red hat's smtp
is converting data to base64...
On 4/15/22 15:36, Daniel Bristot de Oliveira wrote:
> Steven,
>
> Here are some fixes for rtla.
>
> I do not include "rtla/Makefile: Properly handle dependencies"
> because I will make two changes to it:
> - I need to check rst2man only in the make install phase
> - I will remove procps-devel dependency on another patch
>
> I will send a v2 of the "Properly handle dependencies" and the removal
> of procps-devel dependencies next week. But these ones are already ready.
> 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
>
> tools/tracing/rtla/Makefile | 3 ++-
> tools/tracing/rtla/README.txt | 12 +++++-------
> 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 ++++++-----
> 6 files changed, 27 insertions(+), 24 deletions(-)
>
prev parent reply other threads:[~2022-04-19 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 13:36 [PATCH 0/3] rtla: v5.18-rc2 Fixes Daniel Bristot de Oliveira
2022-04-15 13:36 ` [PATCH 1/3] rtla: Avoid record NULL pointer dereference Daniel Bristot de Oliveira
2022-04-15 13:36 ` [PATCH 2/3] rtla: Don't overwrite existing directory mode Daniel Bristot de Oliveira
2022-04-15 13:36 ` [PATCH 3/3] rtla: Minor grammar fix for rtla README Daniel Bristot de Oliveira
2022-04-19 16:23 ` Daniel Bristot de Oliveira [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=d63d91c6-a466-0ca1-9d0d-76ad37f9eff9@kernel.org \
--to=bristot@kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).