From: Markus Elfring <Markus.Elfring@web.de>
To: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
bpf@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Alan Maguire <alan.maguire@oracle.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Florent Revest <revest@chromium.org>,
Jiri Olsa <jolsa@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [for-next][PATCH 15/18] selftests: ftrace: Remove obsolate maxactive syntax check
Date: Sat, 28 Dec 2024 15:48:04 +0100 [thread overview]
Message-ID: <33a2b169-150b-4015-abce-791da3d1c32b@web.de> (raw)
In-Reply-To: <20241227151403.121602937@goodmis.org>
> Since the fprobe event does not support maxactive anymore, stop
> testing the maxactive syntax error checking.
Please avoid a typo in the summary phrase.
Regards,
Markus
next prev parent reply other threads:[~2024-12-28 14:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241227151335.898746489@goodmis.org>
2024-12-27 15:13 ` [for-next][PATCH 01/18] fgraph: Pass ftrace_regs to entryfunc Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 02/18] fgraph: Replace fgraph_ret_regs with ftrace_regs Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 03/18] fgraph: Pass ftrace_regs to retfunc Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 04/18] fprobe: Use ftrace_regs in fprobe entry handler Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 05/18] fprobe: Use ftrace_regs in fprobe exit handler Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 06/18] tracing: Add ftrace_partial_regs() for converting ftrace_regs to pt_regs Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 07/18] tracing: Add ftrace_fill_perf_regs() for perf event Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 08/18] tracing/fprobe: Enable fprobe events with CONFIG_DYNAMIC_FTRACE_WITH_ARGS Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 09/18] bpf: Enable kprobe_multi feature if CONFIG_FPROBE is enabled Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 10/18] ftrace: Add CONFIG_HAVE_FTRACE_GRAPH_FUNC Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 11/18] s390/tracing: Enable HAVE_FTRACE_GRAPH_FUNC Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 12/18] fprobe: Rewrite fprobe on function-graph tracer Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 13/18] fprobe: Add fprobe_header encoding feature Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 14/18] tracing/fprobe: Remove nr_maxactive from fprobe Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 15/18] selftests: ftrace: Remove obsolate maxactive syntax check Steven Rostedt
2024-12-28 14:48 ` Markus Elfring [this message]
2024-12-27 15:13 ` [for-next][PATCH 16/18] selftests/ftrace: Add a test case for repeating register/unregister fprobe Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 17/18] Documentation: probes: Update fprobe on function-graph tracer Steven Rostedt
2024-12-27 15:13 ` [for-next][PATCH 18/18] ftrace: Add ftrace_get_symaddr to convert fentry_ip to symaddr 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=33a2b169-150b-4015-abce-791da3d1c32b@web.de \
--to=markus.elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=alan.maguire@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=revest@chromium.org \
--cc=rostedt@goodmis.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