[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250730100155.268d2442@gandalf.local.home>
Date: Wed, 30 Jul 2025 10:01:55 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Cc: kernel test robot <lkp@...el.com>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
oe-kbuild-all@...ts.linux.dev, Mark Rutland <mark.rutland@....com>, Mathieu
Desnoyers <mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>, Linux Memory Management List
<linux-mm@...ck.org>, Namhyung Kim <namhyung@...nel.org>, Jonathan Corbet
<corbet@....net>, Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH v2 1/2] tracing: Have eprobes have their own config
option
On Wed, 30 Jul 2025 22:57:22 +0900
Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
> > I see you already did the probe pull request.
>
> Ah, I thought this was for the next one... (but I think it is a kind of bugfix?)
Yeah, as its not adding eprobes, but just making it configurable.
But you haven't answered my question ;-)
Do you want to push it to Linus or should I?
I still have the trace/for-next to push (I've finished testing your last
"attribute" patch and now I'm just letting it simmer in linux-next before
doing the pull request). I can still add this to that one if you want.
-- Steve
Powered by blists - more mailing lists