From: Steven Rostedt <rostedt@kernel.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/2] tracing: Fixes for 7.1
Date: Sun, 17 May 2026 09:01:50 -0400 [thread overview]
Message-ID: <20260517130150.399923268@kernel.org> (raw)
tracing fixes for 7.1:
- Add more functions to the remote allowed list
randconfig found more functions that are allowed for the remote code for
s390 and arm. Add them to the allowed list.
- Fix remote_test error path
If one of the simple ring buffers fails to load, the code is supposed to
rollback its initialized buffers. Instead of rolling back the buffers for
the failed load, it uses the global variable and rolls back all the
successfully loaded buffers.
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/fixes
Head SHA1: 55a0005518195fdea1fd2991b07644f8dc97ea8e
Arnd Bergmann (1):
ring-buffer remote: Avoid unexpected symbol warnings (arm, s390)
Vincent Donnefort (1):
tracing: Fix desc in error path for the trace remote test module
----
kernel/trace/Makefile | 4 ++--
kernel/trace/remote_test.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2026-05-17 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 13:01 Steven Rostedt [this message]
2026-05-17 13:01 ` [for-linus][PATCH 1/2] ring-buffer remote: Avoid unexpected symbol warnings (arm, s390) Steven Rostedt
2026-05-17 13:01 ` [for-linus][PATCH 2/2] tracing: Fix desc in error path for the trace remote test module Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2026-05-21 20:45 [for-linus][PATCH 0/2] tracing: Fixes for 7.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=20260517130150.399923268@kernel.org \
--to=rostedt@kernel.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.