From: "Arnd Bergmann" <arnd@arndb.de>
To: "Vincent Donnefort" <vdonnefort@google.com>,
"Steven Rostedt" <rostedt@goodmis.org>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Marc Zyngier" <maz@kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: samples: avoid warning about __aeabi_unwind_cpp_pr1
Date: Fri, 15 May 2026 12:56:44 +0200 [thread overview]
Message-ID: <9668c1fb-2461-4ec4-afbf-80c051aa4064@app.fastmail.com> (raw)
In-Reply-To: <agWb6DvB1MdJ12cB@google.com>
On Thu, May 14, 2026, at 11:54, Vincent Donnefort wrote:
> On Wed, May 13, 2026 at 10:59:39AM -0400, Steven Rostedt wrote:
>>
>> Vincent,
>>
>> Is this patch needed? That is, did it fall through the cracks?
>
> Yes, I believe it is!
>
> Reviewed-by: Vincent Donnefort <vdonnefort@google.com>
Just today, I came across yet another one:
Unexpected symbols in kernel/trace/simple_ring_buffer.o:
U __s390_indirect_jump_r1
U __s390_indirect_jump_r10
U __s390_indirect_jump_r14
U __s390_indirect_jump_r2
U __s390_indirect_jump_r5
U __s390_indirect_jump_r7
U __s390_indirect_jump_r8
U __s390_indirect_jump_r9
I'll send a replacement patch that addresses both, since the
old one hasn't been applied yet.
Arnd
prev parent reply other threads:[~2026-05-15 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 10:56 [PATCH] tracing: samples: avoid warning about __aeabi_unwind_cpp_pr1 Arnd Bergmann
2026-05-13 14:59 ` Steven Rostedt
2026-05-14 9:54 ` Vincent Donnefort
2026-05-15 10:56 ` Arnd Bergmann [this message]
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=9668c1fb-2461-4ec4-afbf-80c051aa4064@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=rostedt@goodmis.org \
--cc=vdonnefort@google.com \
/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