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/5] tracing: Updates for 6.3
Date: Thu, 16 Feb 2023 19:49:54 -0500 [thread overview]
Message-ID: <20230217004954.719324747@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next
Head SHA1: d8f0ae3ebed416728077fe94698983c30d409241
Steven Rostedt (Google) (1):
tracing: Add BUILD_BUG() to make sure stacktrace fits in strings
Tom Zanussi (4):
tracing/histogram: Don't use strlen to find length of stacktrace variables
tracing/histogram: Fix a few problems with stacktrace variable printing
tracing/histogram: Fix stacktrace key
tracing/histogram: Fix stacktrace histogram Documententation
----
Documentation/trace/histogram.rst | 156 ++++++++++++++++++++++----------------
kernel/trace/trace_events_hist.c | 75 ++++++++++++++----
kernel/trace/trace_events_synth.c | 7 +-
3 files changed, 156 insertions(+), 82 deletions(-)
next reply other threads:[~2023-02-17 0:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 0:49 Steven Rostedt [this message]
2023-02-17 0:49 ` [for-next][PATCH 1/5] tracing/histogram: Dont use strlen to find length of stacktrace variables Steven Rostedt
2023-02-17 0:49 ` [for-next][PATCH 2/5] tracing: Add BUILD_BUG() to make sure stacktrace fits in strings Steven Rostedt
2023-02-17 0:49 ` [for-next][PATCH 3/5] tracing/histogram: Fix a few problems with stacktrace variable printing Steven Rostedt
2023-02-17 0:49 ` [for-next][PATCH 4/5] tracing/histogram: Fix stacktrace key Steven Rostedt
2023-02-17 0:49 ` [for-next][PATCH 5/5] tracing/histogram: Fix stacktrace histogram Documententation 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=20230217004954.719324747@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
all inboxes | Powered by JetHome®