public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] tracing/probes: Fixes for v6.5-rc2
Date: Mon, 24 Jul 2023 22:40:17 -0400	[thread overview]
Message-ID: <20230724224017.76d5b0e9@rorschach.local.home> (raw)
In-Reply-To: <169024903018.395371.1006584451160707296.stgit@devnote2>

On Tue, 25 Jul 2023 10:37:10 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:

> These two patches are probe-events fixes for v6.5-rc2.
> One is to fix btf_type_by_id() return value check and the other is fixing
> selftest.
> 
> Thank you,
> 
> ---
> 
> Masami Hiramatsu (Google) (2):
>       tracing/probes: Fix to add NULL check for BTF APIs
>       selftests/ftrace: Fix to check fprobe event eneblement

For both patches:

Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>

-- Steve

> 
> 
>  kernel/trace/trace_probe.c                         |    8 ++++----
>  .../ftrace/test.d/dynevent/add_remove_btfarg.tc    |    2 +-
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 
> --
> Masami Hiramatsu (Google) <mhiramat@kernel.org>


  parent reply	other threads:[~2023-07-25  2:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  1:37 [PATCH 0/2] tracing/probes: Fixes for v6.5-rc2 Masami Hiramatsu (Google)
2023-07-25  1:37 ` [PATCH 1/2] tracing/probes: Fix to add NULL check for BTF APIs Masami Hiramatsu (Google)
2023-07-25  1:37 ` [PATCH 2/2] selftests/ftrace: Fix to check fprobe event eneblement Masami Hiramatsu (Google)
2023-07-25  2:40 ` Steven Rostedt [this message]
2023-07-26  1:44   ` [PATCH 0/2] tracing/probes: Fixes for v6.5-rc2 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=20230724224017.76d5b0e9@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.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