* [PATCH v2] zonefs: correct some spelling mistakes
@ 2025-08-08 8:37 Xichao Zhao
2025-08-12 5:18 ` Damien Le Moal
0 siblings, 1 reply; 2+ messages in thread
From: Xichao Zhao @ 2025-08-08 8:37 UTC (permalink / raw)
To: dlemoal, naohiro.aota; +Cc: jth, linux-fsdevel, linux-kernel, Xichao Zhao
Trivial fix to spelling mistake in comment text.
(1) fix "unwriten"->"unwritten"
(2) fix "writen"->"written"
Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
---
fs/zonefs/file.c | 2 +-
fs/zonefs/super.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
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;
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v2] zonefs: correct some spelling mistakes
2025-08-08 8:37 [PATCH v2] zonefs: correct some spelling mistakes Xichao Zhao
@ 2025-08-12 5:18 ` Damien Le Moal
0 siblings, 0 replies; 2+ messages in thread
From: Damien Le Moal @ 2025-08-12 5:18 UTC (permalink / raw)
To: Xichao Zhao, naohiro.aota; +Cc: jth, linux-fsdevel, linux-kernel
On 8/8/25 5:37 PM, Xichao Zhao wrote:
> Trivial fix to spelling mistake in comment text.
>
> (1) fix "unwriten"->"unwritten"
> (2) fix "writen"->"written"
>
> Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>
Applied to for-6.18. Thanks !
--
Damien Le Moal
Western Digital Research
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-08-12 5:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-08 8:37 [PATCH v2] zonefs: correct some spelling mistakes Xichao Zhao
2025-08-12 5:18 ` Damien Le Moal
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).