Merge tag 'zonefs-6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/zonefs

Pull zonefs update from Damien Le Moal:

- Some comment spelling fixes (Xichao)

* tag 'zonefs-6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/zonefs:
zonefs: correct some spelling mistakes

+3 -3
+1 -1
fs/zonefs/file.c
··· 85 85 /* 86 86 * For conventional zones, all blocks are always mapped. For sequential 87 87 * zones, all blocks after always mapped below the inode size (zone 88 - * write pointer) and unwriten beyond. 88 + * write pointer) and unwritten beyond. 89 89 */ 90 90 mutex_lock(&zi->i_truncate_mutex); 91 91 iomap->bdev = inode->i_sb->s_bdev;
+2 -2
fs/zonefs/super.c
··· 268 268 * Check the zone condition: if the zone is not "bad" (offline or 269 269 * read-only), read errors are simply signaled to the IO issuer as long 270 270 * as there is no inconsistency between the inode size and the amount of 271 - * data writen in the zone (data_size). 271 + * data written in the zone (data_size). 272 272 */ 273 273 data_size = zonefs_check_zone_condition(sb, z, zone); 274 274 isize = i_size_read(inode); ··· 282 282 * For the latter case, the cause may be a write IO error or an external 283 283 * action on the device. Two error patterns exist: 284 284 * 1) The inode size is lower than the amount of data in the zone: 285 - * a write operation partially failed and data was writen at the end 285 + * a write operation partially failed and data was written at the end 286 286 * of the file. This can happen in the case of a large direct IO 287 287 * needing several BIOs and/or write requests to be processed. 288 288 * 2) The inode size is larger than the amount of data in the zone: