linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Martin KaFai Lau <martin.lau@linux.dev>,
	bpf@vger.kernel.org, Sven Schnelle <svens@linux.ibm.com>,
	Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH v5 0/9] tracing: Improbe BTF support on probe events
Date: Tue, 22 Aug 2023 23:38:55 +0900	[thread overview]
Message-ID: <20230822233855.94b653a4bf37b2e93739daa6@kernel.org> (raw)
In-Reply-To: <20230822100716.2dd867e0@rorschach.local.home>

On Tue, 22 Aug 2023 10:07:16 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Tue, 22 Aug 2023 00:09:39 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> 
> > Hi Steve,
> > 
> > Can you review this series?
> > I would like to push this to for-next.
> > 
> 
> I skimmed the patches and played a little with it, but as I've just
> started my vacation I will not be able to do a full review before the
> next merge window. But I don't want me to be the cause of you not
> getting it in.
> 
> Feel free to add:
> 
> Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> 
> to the entire series. I'm sure I'll be playing with it after it gets
> in, and we can fix any bugs that come up then.

Thanks! I'll fix a bit about anon_stack thing and push it to probes/for-next.


> 
> -- Steve


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2023-08-22 14:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  2:54 [PATCH v5 0/9] tracing: Improbe BTF support on probe events Masami Hiramatsu (Google)
2023-08-07  2:54 ` [PATCH v5 1/9] tracing/probes: Support BTF argument on module functions Masami Hiramatsu (Google)
2023-08-07  2:54 ` [PATCH v5 2/9] tracing/probes: Move finding func-proto API and getting func-param API to trace_btf Masami Hiramatsu (Google)
2023-08-07  2:54 ` [PATCH v5 3/9] tracing/probes: Add a function to search a member of a struct/union Masami Hiramatsu (Google)
2023-08-22 13:37   ` Steven Rostedt
2023-08-22 14:36     ` Masami Hiramatsu
2023-08-07  2:55 ` [PATCH v5 4/9] tracing/probes: Support BTF based data structure field access Masami Hiramatsu (Google)
2023-08-07  2:55 ` [PATCH v5 5/9] tracing/probes: Support BTF field access from $retval Masami Hiramatsu (Google)
2023-08-07  2:55 ` [PATCH v5 6/9] tracing/probes: Add string type check with BTF Masami Hiramatsu (Google)
2023-08-07  2:55 ` [PATCH v5 7/9] tracing/fprobe-event: Assume fprobe is a return event by $retval Masami Hiramatsu (Google)
2023-08-07  2:55 ` [PATCH v5 8/9] selftests/ftrace: Add BTF fields access testcases Masami Hiramatsu (Google)
2023-08-07  2:55 ` [PATCH v5 9/9] Documentation: tracing: Update fprobe event example with BTF field Masami Hiramatsu (Google)
2023-08-21 15:09 ` [PATCH v5 0/9] tracing: Improbe BTF support on probe events Masami Hiramatsu
2023-08-22 14:07   ` Steven Rostedt
2023-08-22 14:38     ` Masami Hiramatsu [this message]
2023-08-22 14:46     ` Masami Hiramatsu

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=20230822233855.94b653a4bf37b2e93739daa6@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).