From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
Subject: [for-next][PATCH 0/4] rtla: Updates for 5.20
Date: Sun, 31 Jul 2022 17:09:18 -0400 [thread overview]
Message-ID: <20220731210918.097591536@goodmis.org> (raw)
Andreas Schwab (2):
rtla: Fix double free
rtla: Define syscall numbers for riscv
Daniel Bristot de Oliveira (1):
rtla: Fix Makefile when called from -C tools/
jianchunfu (1):
rtla/utils: Use calloc and check the potential memory allocation failure
----
tools/tracing/rtla/Makefile | 2 +-
tools/tracing/rtla/src/trace.c | 9 +++++++--
tools/tracing/rtla/src/utils.c | 7 ++++---
3 files changed, 12 insertions(+), 6 deletions(-)
next reply other threads:[~2022-07-31 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 21:09 Steven Rostedt [this message]
2022-07-31 21:09 ` [for-next][PATCH 1/4] rtla/utils: Use calloc and check the potential memory allocation failure Steven Rostedt
2022-07-31 21:09 ` [for-next][PATCH 2/4] rtla: Fix Makefile when called from -C tools/ Steven Rostedt
2022-07-31 21:09 ` [for-next][PATCH 3/4] rtla: Fix double free Steven Rostedt
2022-07-31 21:09 ` [for-next][PATCH 4/4] rtla: Define syscall numbers for riscv Steven Rostedt
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=20220731210918.097591536@goodmis.org \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=linux-kernel@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