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-next][PATCH 0/8] tracing: Updates for 5.19
Date: Thu, 28 Apr 2022 17:51:02 -0400 [thread overview]
Message-ID: <20220428215102.260147624@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next-core
Head SHA1: ba27d8555867b0e02e15709f4ddb79aec5cf2efc
Jakob Koschel (4):
tracing: Remove usage of list iterator after the loop body
tracing: Remove usage of list iterator variable after the loop
tracing: Replace usage of found with dedicated list iterator variable
tracing: Remove check of list iterator against head past the loop body
Kurt Kanzenbach (2):
tracing: Introduce trace clock tai
tracing: Add documentation for trace clock tai
Steven Rostedt (Google) (2):
ring-buffer: Have absolute time stamps handle large numbers
ring-buffer: Have 32 bit time stamps use all 64 bits
----
Documentation/trace/ftrace.rst | 12 ++++++
kernel/trace/ftrace.c | 20 ++++++----
kernel/trace/ring_buffer.c | 77 +++++++++++++++++++++++++++++--------
kernel/trace/trace.c | 1 +
kernel/trace/trace_eprobe.c | 14 ++++---
kernel/trace/trace_events.c | 27 +++++++------
kernel/trace/trace_events_hist.c | 15 ++++----
kernel/trace/trace_events_trigger.c | 24 ++++++------
kernel/trace/trace_output.c | 13 +++++--
9 files changed, 135 insertions(+), 68 deletions(-)
next reply other threads:[~2022-04-28 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 21:51 Steven Rostedt [this message]
2022-04-28 21:51 ` [for-next][PATCH 1/8] ring-buffer: Have absolute time stamps handle large numbers Steven Rostedt
2022-04-28 21:51 ` [for-next][PATCH 2/8] ring-buffer: Have 32 bit time stamps use all 64 bits Steven Rostedt
2022-04-28 21:51 ` [for-next][PATCH 3/8] tracing: Introduce trace clock tai Steven Rostedt
2022-04-28 21:51 ` [for-next][PATCH 4/8] tracing: Add documentation for " Steven Rostedt
2022-04-28 21:51 ` [for-next][PATCH 5/8] tracing: Remove usage of list iterator after the loop body Steven Rostedt
2022-04-28 21:51 ` [for-next][PATCH 6/8] tracing: Remove usage of list iterator variable after the loop Steven Rostedt
2022-04-28 21:51 ` [for-next][PATCH 7/8] tracing: Replace usage of found with dedicated list iterator variable Steven Rostedt
2022-04-28 21:51 ` [for-next][PATCH 8/8] tracing: Remove check of list iterator against head past the loop body 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=20220428215102.260147624@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