Skip to contentSkip to conversation

ext2: trivial: fix a typo on comment in ext2/inode.c

PATCH New Namhyung Kim 2 participants 3 messages Sep 8, 2010 – Sep 23, 2010 ext2 file system

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ext2: trivial: fix a typo on comment in ext2/inode.c

'ext3_get_branch' should be 'ext2_get_branch'.

---
 fs/ext2/inode.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
fs/ext2/inode.c +1 -1
index 940c961..860d715 100644
@@ -662,7 +662,7 @@ static int ext2_get_blocks(struct inode *inode,
 	mutex_lock(&ei->truncate_mutex);
 	/*
 	 * If the indirect block is missing while we are reading
-	 * the chain(ext3_get_branch() returns -EAGAIN err), or
+	 * the chain(ext2_get_branch() returns -EAGAIN err), or
 	 * if the chain has been changed after we grab the semaphore,
 	 * (either because another process truncated this branch, or
 	 * another get_block allocated this branch) re-grab the chain to see if
Signature · 1 line
1.7.2.2
#1 lore raw

PATCH 1/1 ext2: trivial: fix typo on comments in ext2/inode.c

'excpet' should be 'except'.
'ext3_get_branch' should be 'ext2_get_branch'.

---
I found another one.

fs/ext2/inode.c +2 -2
index 940c961..533699c 100644
@@ -458,7 +458,7 @@ failed_out:
  *     the same format as ext2_get_branch() would do. We are calling it after
  *     we had read the existing part of chain and partial points to the last
  *     triple of that (one with zero ->key). Upon the exit we have the same
- *     picture as after the successful ext2_get_block(), excpet that in one
+ *     picture as after the successful ext2_get_block(), except that in one
  *     place chain is disconnected - *branch->p is still zero (we did not
  *     set the last link), but branch->key contains the number that should
  *     be placed into *branch->p to fill that gap.
@@ -662,7 +662,7 @@ static int ext2_get_blocks(struct inode *inode,
        mutex_lock(&ei->truncate_mutex);
        /*
         * If the indirect block is missing while we are reading
-        * the chain(ext3_get_branch() returns -EAGAIN err), or
+        * the chain(ext2_get_branch() returns -EAGAIN err), or
         * if the chain has been changed after we grab the semaphore,
         * (either because another process truncated this branch, or
         * another get_block allocated this branch) re-grab the chain to see if
Signature · 1 line
1.7.2.2
Applied
#2 lore raw

Re: [PATCH UPDATED] ext2: trivial: fix typo on comments in ext2/inode.c

Quoted 22 lines · Namhyung Kim

'excpet' should be 'except'.
'ext3_get_branch' should be 'ext2_get_branch'.

---
I found another one.

fs/ext2/inode.c +1 -1
index 940c961..533699c 100644
@@ -458,7 +458,7 @@ failed_out:
  *     the same format as ext2_get_branch() would do. We are calling it after
  *     we had read the existing part of chain and partial points to the last
  *     triple of that (one with zero ->key). Upon the exit we have the same
- *     picture as after the successful ext2_get_block(), excpet that in one
+ *     picture as after the successful ext2_get_block(), except that in one
  *     place chain is disconnected - *branch->p is still zero (we did not
  *     set the last link), but branch->key contains the number that should
  *     be placed into *branch->p to fill that gap.

fs/ext2/inode.c static int ext2_get_blocks(struct inode *inode, · line 668

Quoted 8 lines
fs/ext2/inode.c +1 -1
@@ -662,7 +662,7 @@ static int ext2_get_blocks(struct inode *inode,
        mutex_lock(&ei->truncate_mutex);
        /*
         * If the indirect block is missing while we are reading
-        * the chain(ext3_get_branch() returns -EAGAIN err), or
+        * the chain(ext2_get_branch() returns -EAGAIN err), or
         * if the chain has been changed after we grab the semaphore,
         * (either because another process truncated this branch, or
         * another get_block allocated this branch) re-grab the chain to see if

Applied.

Signature · 2 lines
Jiri Kosina
SUSE Labs, Novell Inc.