From: Heiko Carstens <hca@linux.ibm.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Sven Schnelle <svens@linux.ibm.com>,
Jiri Olsa <olsajiri@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH 0/2] tracing: s390: Fix fprobes on s390
Date: Wed, 29 Jan 2025 10:12:26 +0100 [thread overview]
Message-ID: <20250129091226.10055-A-hca@linux.ibm.com> (raw)
In-Reply-To: <173807816551.1854334.146350914633413330.stgit@devnote2>
On Wed, Jan 29, 2025 at 12:29:25AM +0900, Masami Hiramatsu (Google) wrote:
> Hi,
>
> Here are fprobe and kprobe-multi fix patches for s390 which maybe broken
> when we introduced fprobes on fgraph series.
>
> Thank you,
>
> ---
>
> Masami Hiramatsu (Google) (2):
> s390: fgraph: Fix to remove ftrace_test_recursion_trylock()
> s390: tracing: Define ftrace_get_symaddr() for s390
>
>
> arch/s390/include/asm/ftrace.h | 1 +
> arch/s390/kernel/ftrace.c | 5 -----
> 2 files changed, 1 insertion(+), 5 deletions(-)
For both patches:
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
prev parent reply other threads:[~2025-01-29 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 15:29 [PATCH 0/2] tracing: s390: Fix fprobes on s390 Masami Hiramatsu (Google)
2025-01-28 15:29 ` [PATCH 1/2] s390: fgraph: Fix to remove ftrace_test_recursion_trylock() Masami Hiramatsu (Google)
2025-01-29 0:36 ` Ihor Solodrai
2025-01-28 15:29 ` [PATCH 2/2] s390: tracing: Define ftrace_get_symaddr() for s390 Masami Hiramatsu (Google)
2025-01-29 9:12 ` Heiko Carstens [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=20250129091226.10055-A-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=andrii.nakryiko@gmail.com \
--cc=borntraeger@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=olsajiri@gmail.com \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.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 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.