[-next] virtiofs: Fix spelling mistakes

Commit Message

Zheng Yongjun June 4, 2021, 1:46 a.m. UTC

Fix some spelling mistakes in comments:
refernce  ==> reference
happnes  ==> happens
threhold  ==> threshold
splitted  ==> split
mached  ==> matched

Signed-off-by: Zheng Yongjun <[e-mail]>
---
 fs/fuse/dax.c  | 6 +++---
 fs/fuse/dev.c  | 2 +-
 fs/fuse/file.c | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

Comments

Miklos Szeredi June 21, 2021, 8:44 a.m. UTC | #1

On Fri, 4 Jun 2021 at 03:32, Zheng Yongjun <[e-mail]> wrote:
>
> Fix some spelling mistakes in comments:
> refernce  ==> reference
> happnes  ==> happens
> threhold  ==> threshold
> splitted  ==> split
> mached  ==> matched
>
> Signed-off-by: Zheng Yongjun <[e-mail]>

Thanks, applied.

Miklos

Patch

diff --git a/fs/fuse/dax.c b/fs/fuse/dax.c
index ff99ab2a3c43..a005859d1c1c 100644
--- a/fs/fuse/dax.c
+++ b/fs/fuse/dax.c
@@ -212,7 +212,7 @@  static int fuse_setup_one_mapping(struct inode *inode, unsigned long start_idx,
 	dmap->writable = writable;
 	if (!upgrade) {
 		/*
-		 * We don't take a refernce on inode. inode is valid right now
+		 * We don't take a reference on inode. inode is valid right now
 		 * and when inode is going away, cleanup logic should first
 		 * cleanup dmap entries.
 		 */
@@ -621,7 +621,7 @@  static int fuse_iomap_begin(struct inode *inode, loff_t pos, loff_t length,
 	}
 
 	/*
-	 * If read beyond end of file happnes, fs code seems to return
+	 * If read beyond end of file happens, fs code seems to return
 	 * it as hole
 	 */
 iomap_hole:
@@ -1206,7 +1206,7 @@  static void fuse_dax_free_mem_worker(struct work_struct *work)
 			 ret);
 	}
 
-	/* If number of free ranges are still below threhold, requeue */
+	/* If number of free ranges are still below threshold, requeue */
 	kick_dmap_free_worker(fcd, 1);
 }
 
diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
index a5ceccc5ef00..0252933eb905 100644
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -91,7 +91,7 @@  static void fuse_drop_waiting(struct fuse_conn *fc)
 {
 	/*
 	 * lockess check of fc->connected is okay, because atomic_dec_and_test()
-	 * provides a memory barrier mached with the one in fuse_wait_aborted()
+	 * provides a memory barrier matched with the one in fuse_wait_aborted()
 	 * to ensure no wake-up is missed.
 	 */
 	if (atomic_dec_and_test(&fc->num_waiting) &&
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index 09ef2a4d25ed..6084552f685f 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -645,7 +645,7 @@  static ssize_t fuse_get_res_by_io(struct fuse_io_priv *io)
  * == bytes_transferred or rw == WRITE, the caller sets 'pos' to -1.
  *
  * An example:
- * User requested DIO read of 64K. It was splitted into two 32K fuse requests,
+ * User requested DIO read of 64K. It was split into two 32K fuse requests,
  * both submitted asynchronously. The first of them was ACKed by userspace as
  * fully completed (req->out.args[0].size == 32K) resulting in pos == -1. The
  * second request was ACKed as short, e.g. only 1K was read, resulting in