From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/2] tracing: Last two fixes before pushing to 6.1
Date: Wed, 05 Oct 2022 22:21:26 -0400 [thread overview]
Message-ID: <20221006022126.894976366@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: a541a9559bb0a8ecc434de01d3e4826c32e8bb53
Steven Rostedt (Google) (2):
ftrace: Still disable enabled records marked as disabled
tracing: Do not free snapshot if tracer is on cmdline
----
kernel/trace/ftrace.c | 20 ++++++++++++++++----
kernel/trace/trace.c | 10 ++++++----
2 files changed, 22 insertions(+), 8 deletions(-)
next reply other threads:[~2022-10-06 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 2:21 Steven Rostedt [this message]
2022-10-06 2:21 ` [for-next][PATCH 1/2] ftrace: Still disable enabled records marked as disabled Steven Rostedt
2022-10-06 2:21 ` [for-next][PATCH 2/2] tracing: Do not free snapshot if tracer is on cmdline Steven Rostedt
2022-10-06 2:27 ` [for-next][PATCH 0/2] tracing: Last two fixes before pushing to 6.1 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=20221006022126.894976366@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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