From: Bean Huo <huobean@gmail.com>
To: rostedt@goodmis.org, mingo@redhat.com, beanhuo@micron.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] tracing: Fix two compiling warnings
Date: Tue, 12 Jan 2021 12:12:02 +0100 [thread overview]
Message-ID: <20210112111202.23508-1-huobean@gmail.com> (raw)
From: Bean Huo <beanhuo@micron.com>
Add description for two function parameters, to fix below two warnings:
kernel/trace/trace.c:464: warning: Function parameter or member 'this_tr' not described in 'trace_array_put'
kernel/trace/trace.c:543: warning: Function parameter or member 'filtered_no_pids' not described in 'trace_ignore_this_task'
Signed-off-by: Bean Huo <beanhuo@micron.com>
---
kernel/trace/trace.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index b8a2d786b503..8edcd91ed172 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -454,6 +454,7 @@ static void __trace_array_put(struct trace_array *this_tr)
/**
* trace_array_put - Decrement the reference counter for this trace array.
+ * @this_tr : pointer to the trace array
*
* NOTE: Use this when we no longer need the trace array returned by
* trace_array_get_by_name(). This ensures the trace array can be later
@@ -530,6 +531,7 @@ trace_find_filtered_pid(struct trace_pid_list *filtered_pids, pid_t search_pid)
/**
* trace_ignore_this_task - should a task be ignored for tracing
* @filtered_pids: The list of pids to check
+ * @filtered_no_pids: The list of pids that not be traced by the function tracer
* @task: The task that should be ignored if not filtered
*
* Checks if @task should be traced or not from @filtered_pids.
--
2.17.1
reply other threads:[~2021-01-12 11:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210112111202.23508-1-huobean@gmail.com \
--to=huobean@gmail.com \
--cc=beanhuo@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).