All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Yuntao Wang <ytcoode@gmail.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing: Deal with error return code of the ftrace_process_locs() function
Date: Tue, 24 May 2022 13:24:34 -0400	[thread overview]
Message-ID: <20220524132434.3cf03936@gandalf.local.home> (raw)
In-Reply-To: <20220120065949.1813231-1-ytcoode@gmail.com>

On Thu, 20 Jan 2022 06:59:49 +0000
Yuntao Wang <ytcoode@gmail.com> wrote:

> The ftrace_process_locs() function may return -ENOMEM error code, which
> should be handled by the callers.
> 
> Signed-off-by: Yuntao Wang <ytcoode@gmail.com>
> ---
> Changes since v1:
> - Deal with error return code instead of just removing it
> 
> 

Thanks, I added this to my queue. Note, I renamed the subject to start with
"ftrace:" instead of "tracing:" as this is specific to ftrace (the function
hook infrastructure).

-- Steve

      reply	other threads:[~2022-05-24 17:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16 14:48 [PATCH] tracing: Remove redundant assignment to variable ret Yuntao Wang
2022-01-17  7:41 ` [PATCH] tracing: Remove redundant assignment to variable ret' Lukas Bulwahn
2022-01-19  4:17   ` [PATCH] tracing: Remove redundant assignment to variable ret Yuntao Wang
2022-01-19  7:15     ` Lukas Bulwahn
2022-01-19 14:57       ` Steven Rostedt
2022-01-20  6:59         ` [PATCH v2] tracing: Deal with error return code of the ftrace_process_locs() function Yuntao Wang
2022-05-24 17:24           ` Steven Rostedt [this message]

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=20220524132434.3cf03936@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mingo@redhat.com \
    --cc=ytcoode@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.