From: Ankit Thakur <codeankit.thakur@gmail.com>
To: Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Dominique Martinet <asmadeus@codewreck.org>
Cc: Christian Schoenebeck <linux_oss@crudebyte.com>,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
Ankit Thakur <codeankit.thakur@gmail.com>
Subject: [PATCH 2/4] 9p: fix typos and wrong parameter docs in vfs_inode.c
Date: Sat, 24 Oct 2026 14:51:52 +0530 [thread overview]
Message-ID: <20261024092154.1844-2-codeankit.thakur@gmail.com> (raw)
In-Reply-To: <20261024092154.1844-1-codeankit.thakur@gmail.com>
Fix spelling mistakes in comments (functon -> function, Hadlink ->
Hardlink).
Also fix the kernel-doc of v9fs_vfs_mkdir(), which described @dir and
@dentry as being unlinked instead of being the parent directory and the
directory being created.
Signed-off-by: Ankit Thakur <codeankit.thakur@gmail.com>
---
fs/9p/vfs_inode.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/9p/vfs_inode.c b/fs/9p/vfs_inode.c
index 537cb22ac..0585cc915 100644
--- a/fs/9p/vfs_inode.c
+++ b/fs/9p/vfs_inode.c
@@ -481,7 +481,7 @@ static int v9fs_at_to_dotl_flags(int flags)
}
/**
- * v9fs_dec_count - helper functon to drop i_nlink.
+ * v9fs_dec_count - helper function to drop i_nlink.
*
* If a directory had nlink <= 2 (including . and ..), then we should not drop
* the link count, which indicates the underlying exported fs doesn't maintain
@@ -673,8 +673,8 @@ v9fs_vfs_create(const struct mnt_idmap *idmap, struct inode *dir,
/**
* v9fs_vfs_mkdir - VFS mkdir hook to create a directory
* @idmap: idmap of the mount
- * @dir: inode that is being unlinked
- * @dentry: dentry that is being unlinked
+ * @dir: inode of the parent directory
+ * @dentry: dentry representing the directory being created
* @mode: mode for new directory
*
*/
@@ -1134,7 +1134,7 @@ v9fs_stat2inode(struct p9_wstat *stat, struct inode *inode,
if (v9fs_proto_dotu(v9ses)) {
unsigned int i_nlink;
/*
- * Hadlink support got added later to the .u extension.
+ * Hardlink support got added later to the .u extension.
* So there can be a server out there that doesn't
* support this even with .u extension. That would
* just leave us with stat->extension being an empty
--
2.55.0.windows.3
next prev parent reply other threads:[~2026-10-24 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 9:21 [PATCH 1/4] 9p: fix header guard comment in acl.h Ankit Thakur
2026-10-24 9:21 ` Ankit Thakur [this message]
2026-10-24 9:21 ` [PATCH 3/4] 9p: remove duplicated assignment in v9fs_fill_super() Ankit Thakur
2026-10-24 9:21 ` [PATCH 4/4] 9p: fix typo in file header comments Ankit Thakur
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=20261024092154.1844-2-codeankit.thakur@gmail.com \
--to=codeankit.thakur@gmail.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=v9fs@lists.linux.dev \
/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
all inboxes | Powered by JetHome®