From: Bhanu Seshu Kumar Valluri <bhanuseshukumar@gmail.com>
To: Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>, NeilBrown <neil@brown.name>,
Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
Kaixiong Yu <yukaixiong@huawei.com>,
Bhanu Seshu Kumar Valluri <bhanuseshukumar@gmail.com>,
Omar Sandoval <osandov@fb.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org, david.hunter.linux@gmail.com,
linux-kernel@vger.kernel.org
Subject: [PATCH] fs: dcache: Fixed typo in doc comments
Date: Wed, 1 Oct 2025 10:21:45 +0530 [thread overview]
Message-ID: <20251001045145.38769-1-bhanuseshukumar@gmail.com> (raw)
resonsibility => responsibility
Signed-off-by: Bhanu Seshu Kumar Valluri <bhanuseshukumar@gmail.com>
---
Note: No functionality change is intended.
include/linux/dcache.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/dcache.h b/include/linux/dcache.h
index cc3e1c1a3454..17640d7a45aa 100644
--- a/include/linux/dcache.h
+++ b/include/linux/dcache.h
@@ -312,7 +312,7 @@ extern char *dentry_path(const struct dentry *, char *, int);
*
* Given a live dentry, increment the reference count and return the dentry.
* Caller must hold @dentry->d_lock. Making sure that dentry is alive is
- * caller's resonsibility. There are many conditions sufficient to guarantee
+ * caller's responsibility. There are many conditions sufficient to guarantee
* that; e.g. anything with non-negative refcount is alive, so's anything
* hashed, anything positive, anyone's parent, etc.
*/
--
2.34.1
reply other threads:[~2025-10-01 4:52 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=20251001045145.38769-1-bhanuseshukumar@gmail.com \
--to=bhanuseshukumar@gmail.com \
--cc=brauner@kernel.org \
--cc=david.hunter.linux@gmail.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=osandov@fb.com \
--cc=skhan@linuxfoundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yukaixiong@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox