From: Colin Ian King <colin.i.king@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
linux-kernel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: [PATCH][next] firewire: core: Fix spelling mistakes in tracepoint messages
Date: Thu, 27 Jun 2024 18:08:47 +0100 [thread overview]
Message-ID: <20240627170847.125531-1-colin.i.king@gmail.com> (raw)
There are two spelling mistakes in the tracepoint message text. Fix them.
Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
include/trace/events/firewire.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/trace/events/firewire.h b/include/trace/events/firewire.h
index d9158a134beb..86330ba58336 100644
--- a/include/trace/events/firewire.h
+++ b/include/trace/events/firewire.h
@@ -853,7 +853,7 @@ DECLARE_EVENT_CLASS(isoc_single_completions_template,
memcpy(__get_dynamic_array(header), header, __get_dynamic_array_len(header));
),
TP_printk(
- "context=0x%llx card_index=%u timestap=0x%04x cause=%s header=%s",
+ "context=0x%llx card_index=%u timestamp=0x%04x cause=%s header=%s",
__entry->context,
__entry->card_index,
__entry->timestamp,
@@ -891,7 +891,7 @@ TRACE_EVENT(isoc_inbound_multiple_completions,
__entry->cause = cause;
),
TP_printk(
- "context=0x%llx card_index=%u comleted=%u cause=%s",
+ "context=0x%llx card_index=%u completed=%u cause=%s",
__entry->context,
__entry->card_index,
__entry->completed,
--
2.39.2
next reply other threads:[~2024-06-27 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 17:08 Colin Ian King [this message]
2024-06-28 1:06 ` [PATCH][next] firewire: core: Fix spelling mistakes in tracepoint messages Takashi Sakamoto
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=20240627170847.125531-1-colin.i.king@gmail.com \
--to=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=o-takashi@sakamocchi.jp \
--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).