[PATCH 0/6] fs: correct some spelling mistakes

[PATCH 0/6] fs: correct some spelling mistakes

[Xichao Zhao]

Trivial fix to spelling mistake in comment text.


Xichao Zhao (6):
  fs: fix "writen"->"written"
  NFSv4: fix prefered -> preferred
  fsnotify: fix "rewriten"->"rewritten"
  xfs: fix "acheive"->"achieve"
  zonefs: fix "unwriten"->"unwritten"
  zonefs: fix "writen"->"written"

 fs/namei.c                           | 2 +-
 fs/nfs/nfs4xdr.c                     | 2 +-
 fs/notify/inotify/inotify_fsnotify.c | 2 +-
 fs/xfs/xfs_inode.c                   | 2 +-
 fs/zonefs/file.c                     | 2 +-
 fs/zonefs/super.c                    | 4 ++--
 6 files changed, 7 insertions(+), 7 deletions(-)

-- 
2.34.1

[PATCH 1/6] fs: fix "writen"->"written"

[Xichao Zhao]

Trivial fix to spelling mistake in comment text.

Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
---
 fs/namei.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/namei.c b/fs/namei.c
index 044a3011be49..10f7caff7f0f 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -4828,7 +4828,7 @@ int vfs_link(struct dentry *old_dentry, struct mnt_idmap *idmap,
 		return -EPERM;
 	/*
 	 * Updating the link count will likely cause i_uid and i_gid to
-	 * be writen back improperly if their true value is unknown to
+	 * be written back improperly if their true value is unknown to
 	 * the vfs.
 	 */
 	if (HAS_UNMAPPED_ID(idmap, inode))
-- 
2.34.1

[PATCH 3/6] fsnotify: fix "rewriten"->"rewritten"

[Xichao Zhao]

Trivial fix to spelling mistake in comment text.

Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
---
 fs/notify/inotify/inotify_fsnotify.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/notify/inotify/inotify_fsnotify.c b/fs/notify/inotify/inotify_fsnotify.c
index cd7d11b0eb08..7c326ec2e8a8 100644
--- a/fs/notify/inotify/inotify_fsnotify.c
+++ b/fs/notify/inotify/inotify_fsnotify.c
@@ -10,7 +10,7 @@
  * Copyright 2006 Hewlett-Packard Development Company, L.P.
  *
  * Copyright (C) 2009 Eric Paris <Red Hat Inc>
- * inotify was largely rewriten to make use of the fsnotify infrastructure
+ * inotify was largely rewritten to make use of the fsnotify infrastructure
  */
 
 #include <linux/dcache.h> /* d_unlinked */
-- 
2.34.1

[PATCH 5/6] zonefs: fix "unwriten"->"unwritten"

[Xichao Zhao]

Trivial fix to spelling mistake in comment text.

Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
---
 fs/zonefs/file.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/zonefs/file.c b/fs/zonefs/file.c
index fd3a5922f6c3..90e2ad8ee5f4 100644
--- a/fs/zonefs/file.c
+++ b/fs/zonefs/file.c
@@ -85,7 +85,7 @@ static int zonefs_write_iomap_begin(struct inode *inode, loff_t offset,
 	/*
 	 * For conventional zones, all blocks are always mapped. For sequential
 	 * zones, all blocks after always mapped below the inode size (zone
-	 * write pointer) and unwriten beyond.
+	 * write pointer) and unwritten beyond.
 	 */
 	mutex_lock(&zi->i_truncate_mutex);
 	iomap->bdev = inode->i_sb->s_bdev;
-- 
2.34.1

[PATCH 6/6] zonefs: fix "writen"->"written"

[Xichao Zhao]

Trivial fix to spelling mistake in comment text.

Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
---
 fs/zonefs/super.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c
index 4dc7f967c861..70be0b3dda49 100644
--- a/fs/zonefs/super.c
+++ b/fs/zonefs/super.c
@@ -268,7 +268,7 @@ static void zonefs_handle_io_error(struct inode *inode, struct blk_zone *zone,
 	 * Check the zone condition: if the zone is not "bad" (offline or
 	 * read-only), read errors are simply signaled to the IO issuer as long
 	 * as there is no inconsistency between the inode size and the amount of
-	 * data writen in the zone (data_size).
+	 * data written in the zone (data_size).
 	 */
 	data_size = zonefs_check_zone_condition(sb, z, zone);
 	isize = i_size_read(inode);
@@ -282,7 +282,7 @@ static void zonefs_handle_io_error(struct inode *inode, struct blk_zone *zone,
 	 * For the latter case, the cause may be a write IO error or an external
 	 * action on the device. Two error patterns exist:
 	 * 1) The inode size is lower than the amount of data in the zone:
-	 *    a write operation partially failed and data was writen at the end
+	 *    a write operation partially failed and data was written at the end
 	 *    of the file. This can happen in the case of a large direct IO
 	 *    needing several BIOs and/or write requests to be processed.
 	 * 2) The inode size is larger than the amount of data in the zone:
-- 
2.34.1

Re: [PATCH 6/6] zonefs: fix "writen"->"written"

[Damien Le Moal]

On 8/8/25 4:14 PM, Xichao Zhao wrote:
> Trivial fix to spelling mistake in comment text.
> 
> Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>

Please squash this with patch 5/6. There is no good reason to have 2 patches
for typo fixes.

Also split this into separate patches for each FS. The entire patch series is
not going to be applied in a single tree. The different FS maintainers wil (or
not) take the patches for their FS in their tree.

> ---
>  fs/zonefs/super.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c
> index 4dc7f967c861..70be0b3dda49 100644
> --- a/fs/zonefs/super.c
> +++ b/fs/zonefs/super.c
> @@ -268,7 +268,7 @@ static void zonefs_handle_io_error(struct inode *inode, struct blk_zone *zone,
>  	 * Check the zone condition: if the zone is not "bad" (offline or
>  	 * read-only), read errors are simply signaled to the IO issuer as long
>  	 * as there is no inconsistency between the inode size and the amount of
> -	 * data writen in the zone (data_size).
> +	 * data written in the zone (data_size).
>  	 */
>  	data_size = zonefs_check_zone_condition(sb, z, zone);
>  	isize = i_size_read(inode);
> @@ -282,7 +282,7 @@ static void zonefs_handle_io_error(struct inode *inode, struct blk_zone *zone,
>  	 * For the latter case, the cause may be a write IO error or an external
>  	 * action on the device. Two error patterns exist:
>  	 * 1) The inode size is lower than the amount of data in the zone:
> -	 *    a write operation partially failed and data was writen at the end
> +	 *    a write operation partially failed and data was written at the end
>  	 *    of the file. This can happen in the case of a large direct IO
>  	 *    needing several BIOs and/or write requests to be processed.
>  	 * 2) The inode size is larger than the amount of data in the zone:


-- 
Damien Le Moal
Western Digital Research