From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/4] tracing: Small last minute fixes
Date: Wed, 22 May 2024 19:28:51 -0400 [thread overview]
Message-ID: <20240522232851.522913754@goodmis.org> (raw)
tracing: Minor last minute fixes
- Fix a very tight race between the ring buffer readers and resizing
the ring buffer.
- Correct some stale comments in the ring buffer code.
- Fix kernel-doc in the rv code.
- Add a MODULE_DESCRIPTION to preemptirq_delay_test
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/urgent
Head SHA1: 1e8b7b3dbb3103d577a586ca72bc329f7b67120b
Jeff Johnson (1):
tracing: Add MODULE_DESCRIPTION() to preemptirq_delay_test
Petr Pavlu (2):
ring-buffer: Correct stale comments related to non-consuming readers
ring-buffer: Fix a race between readers and resize checks
Yang Li (1):
rv: Update rv_en(dis)able_monitor doc to match kernel-doc
----
kernel/trace/preemptirq_delay_test.c | 1 +
kernel/trace/ring_buffer.c | 25 ++++++++++++-------------
kernel/trace/rv/rv.c | 2 ++
3 files changed, 15 insertions(+), 13 deletions(-)
next reply other threads:[~2024-05-22 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 23:28 Steven Rostedt [this message]
2024-05-22 23:28 ` [for-linus][PATCH 1/4] ring-buffer: Correct stale comments related to non-consuming readers Steven Rostedt
2024-05-22 23:28 ` [for-linus][PATCH 2/4] ring-buffer: Fix a race between readers and resize checks Steven Rostedt
2024-05-22 23:28 ` [for-linus][PATCH 3/4] tracing: Add MODULE_DESCRIPTION() to preemptirq_delay_test Steven Rostedt
2024-05-22 23:28 ` [for-linus][PATCH 4/4] rv: Update rv_en(dis)able_monitor doc to match kernel-doc 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=20240522232851.522913754@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.