From: Namhyung Kim <namhyung@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v13 04/11] perf/probe: Ignore comment lines in dynamic_events/kprobe_events file
Date: Wed, 1 Jul 2026 10:44:22 -0700 [thread overview]
Message-ID: <akVR9oUGIjmheePT@google.com> (raw)
In-Reply-To: <20260701073939.81842d6f6bd139a329c45c7f@kernel.org>
On Wed, Jul 01, 2026 at 07:39:39AM +0900, Masami Hiramatsu wrote:
> On Mon, 29 Jun 2026 17:33:43 -0700
> Namhyung Kim <namhyung@kernel.org> wrote:
>
> > Hi Masami,
> >
> > On Tue, Jun 30, 2026 at 07:32:11AM +0900, Masami Hiramatsu wrote:
> > > Hi Arnaldo, Namhyung,
> > >
> > > I forgot to CC this. Can I pick this patch via linux-trace tree,
> > > or would you pick this?
> > > This is a part of typecast series [1] only for debugging.
> >
> > Thanks for letting me know.
> >
> > I think it's better to route this through the perf tree as we're seeing
> > a lot of cleanups all around the code base. Having this together would
> > reduce chances of future conflicts. Does that sound ok to you?
>
> OK, thanks for confirmation. Then I'll drop it from probes/for-next (and probes/core).
Thanks, I've applied it to perf-tools-next.
Best regards,
Namhyung
next prev parent reply other threads:[~2026-07-01 17:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 6:12 [PATCH v13 00/11] tracing/probes: Add more typecast features Masami Hiramatsu (Google)
2026-06-29 6:13 ` [PATCH v13 01/11] tracing/probes: Allow eprobe to use variable without $ prefix Masami Hiramatsu (Google)
2026-06-29 6:13 ` [PATCH v13 02/11] tracing/probes: Support dumping fetcharg program for debugging dynamic events Masami Hiramatsu (Google)
2026-06-29 6:13 ` [PATCH v13 03/11] tools/bootconfig: Ignore comment lines in dynamic_events/kprobe_events file Masami Hiramatsu (Google)
2026-06-29 6:13 ` [PATCH v13 04/11] perf/probe: " Masami Hiramatsu (Google)
2026-06-29 22:32 ` Masami Hiramatsu
2026-06-30 0:33 ` Namhyung Kim
2026-06-30 22:39 ` Masami Hiramatsu
2026-07-01 17:44 ` Namhyung Kim [this message]
2026-06-29 6:13 ` [PATCH v13 05/11] tracing/probes: Support typecast for various probe events Masami Hiramatsu (Google)
2026-06-29 6:13 ` [PATCH v13 06/11] tracing/probes: Support nested typecast Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 07/11] tracing/probes: Type casting always involves nested calls Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 08/11] tracing/probes: Support field specifier option for typecast Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 09/11] tracing/probes: Add $current variable support Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 10/11] tracing/probes: Add this_cpu_read() and this_cpu_ptr() dereference method to fetcharg Masami Hiramatsu (Google)
2026-06-29 6:14 ` [PATCH v13 11/11] tracing/probes: Add a new testcase for BTF typecasts Masami Hiramatsu (Google)
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=akVR9oUGIjmheePT@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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