From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/3] tracing: Three fixes
Date: Thu, 10 Mar 2022 10:04:31 -0500 [thread overview]
Message-ID: <20220310150431.248810778@goodmis.org> (raw)
Minor tracing fixes:
- Fix unregistering the same event twice a the user could disable
the event osnoise will disable on unregistering.
- Inform RCU of a quiescent state in the osnoise testing thread.
- Fix some kerneldoc comments.
Daniel Bristot de Oliveira (1):
tracing/osnoise: Do not unregister events twice
Jiapeng Chong (1):
ftrace: Fix some W=1 warnings in kernel doc comments
Nicolas Saenz Julienne (1):
tracing/osnoise: Force quiescent states while tracing
----
kernel/trace/ftrace.c | 4 ++--
kernel/trace/trace_osnoise.c | 31 +++++++++++++++++++++++++++++++
2 files changed, 33 insertions(+), 2 deletions(-)
next reply other threads:[~2022-03-10 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 15:04 Steven Rostedt [this message]
2022-03-10 15:04 ` [for-linus][PATCH 1/3] tracing/osnoise: Do not unregister events twice Steven Rostedt
2022-03-10 15:04 ` [for-linus][PATCH 2/3] tracing/osnoise: Force quiescent states while tracing Steven Rostedt
2022-03-10 15:04 ` [for-linus][PATCH 3/3] ftrace: Fix some W=1 warnings in kernel doc comments 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=20220310150431.248810778@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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