From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Gaosheng Cui <cuigaosheng1@huawei.com>
Subject: [for-linus][PATCH 4/7] tracing: Fix kernel-doc warnings in trace_events_trigger.c
Date: Sat, 29 Jul 2023 14:33:37 -0400 [thread overview]
Message-ID: <20230729183421.670475369@goodmis.org> (raw)
In-Reply-To: 20230729183333.357029101@goodmis.org
From: Gaosheng Cui <cuigaosheng1@huawei.com>
Fix kernel-doc warnings:
kernel/trace/trace_events_trigger.c:59: warning: Function parameter
or member 'buffer' not described in 'event_triggers_call'
kernel/trace/trace_events_trigger.c:59: warning: Function parameter
or member 'event' not described in 'event_triggers_call'
Link: https://lkml.kernel.org/r/20230724140827.1023266-4-cuigaosheng1@huawei.com
Cc: <mhiramat@kernel.org>
Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
kernel/trace/trace_events_trigger.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
index e535959939d3..46439e3bcec4 100644
--- a/kernel/trace/trace_events_trigger.c
+++ b/kernel/trace/trace_events_trigger.c
@@ -31,7 +31,9 @@ void trigger_data_free(struct event_trigger_data *data)
/**
* event_triggers_call - Call triggers associated with a trace event
* @file: The trace_event_file associated with the event
+ * @buffer: The ring buffer that the event is being written to
* @rec: The trace entry for the event, NULL for unconditional invocation
+ * @event: The event meta data in the ring buffer
*
* For each trigger associated with an event, invoke the trigger
* function registered with the associated trigger command. If rec is
--
2.40.1
next prev parent reply other threads:[~2023-07-29 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 18:33 [for-linus][PATCH 0/7] tracing: A few more fixes for 6.5 Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 1/7] ring-buffer: Fix wrong stat of cpu_buffer->read Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 2/7] ring-buffer: Fix kernel-doc warnings in ring_buffer.c Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 3/7] tracing/synthetic: Fix kernel-doc warnings in trace_events_synth.c Steven Rostedt
2023-07-29 18:33 ` Steven Rostedt [this message]
2023-07-29 18:33 ` [for-linus][PATCH 5/7] tracing: Fix kernel-doc warnings in trace_seq.c Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 6/7] ftrace: Remove unused extern declarations Steven Rostedt
2023-07-29 18:33 ` [for-linus][PATCH 7/7] tracing: Fix warning in trace_buffered_event_disable() Steven Rostedt
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=20230729183421.670475369@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=cuigaosheng1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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 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.