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>
Subject: [for-next][PATCH 4/4] eventfs: Fix typo in eventfs_inode union comment
Date: Wed, 25 Oct 2023 21:27:38 -0400 [thread overview]
Message-ID: <20231026012754.043877861@goodmis.org> (raw)
In-Reply-To: 20231026012734.358814002@goodmis.org
From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
It's eventfs_inode not eventfs_indoe. There's no deer involved!
Link: https://lore.kernel.org/linux-trace-kernel/20231024131024.5634c743@gandalf.local.home
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Fixes: 5790b1fb3d672 ("eventfs: Remove eventfs_file and just use eventfs_inode")
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
fs/tracefs/internal.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/tracefs/internal.h b/fs/tracefs/internal.h
index 298d3ecaf621..64fde9490f52 100644
--- a/fs/tracefs/internal.h
+++ b/fs/tracefs/internal.h
@@ -37,7 +37,7 @@ struct eventfs_inode {
/*
* Union - used for deletion
* @del_list: list of eventfs_inode to delete
- * @rcu: eventfs_indoe to delete in RCU
+ * @rcu: eventfs_inode to delete in RCU
* @is_freed: node is freed if one of the above is set
*/
union {
--
2.42.0
prev parent reply other threads:[~2023-10-26 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 1:27 [for-next][PATCH 0/4] tracing: Updates for 6.7 Steven Rostedt
2023-10-26 1:27 ` [for-next][PATCH 1/4] tracing/histograms: Simplify last_cmd_set() Steven Rostedt
2023-10-26 1:27 ` [for-next][PATCH 2/4] powerpc: Remove initialisation of readpos Steven Rostedt
2023-10-26 1:27 ` [for-next][PATCH 3/4] eventfs: Fix WARN_ON() in create_file_dentry() Steven Rostedt
2023-10-26 1:27 ` 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=20231026012754.043877861@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox