All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] ext2: trivial: fix a typo on comment in ext2/inode.c
@ 2010-09-08 16:14 Namhyung Kim
  2010-09-10  1:39 ` [PATCH UPDATED] ext2: trivial: fix typo on comments " Namhyung Kim
  0 siblings, 1 reply; 3+ messages in thread
From: Namhyung Kim @ 2010-09-08 16:14 UTC (permalink / raw)
  To: Jiri Kosina, linux-ext4; +Cc: linux-kernel

'ext3_get_branch' should be 'ext2_get_branch'.

Signed-off-by: Namhyung Kim <namhyung@gmail.com>
---
 fs/ext2/inode.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/ext2/inode.c b/fs/ext2/inode.c
index 940c961..860d715 100644
--- a/fs/ext2/inode.c
+++ b/fs/ext2/inode.c
@@ -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
-- 
1.7.2.2


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* [PATCH UPDATED] ext2: trivial: fix typo on comments in ext2/inode.c
  2010-09-08 16:14 [PATCH] ext2: trivial: fix a typo on comment in ext2/inode.c Namhyung Kim
@ 2010-09-10  1:39 ` Namhyung Kim
  2010-09-23 11:50   ` Jiri Kosina
  0 siblings, 1 reply; 3+ messages in thread
From: Namhyung Kim @ 2010-09-10  1:39 UTC (permalink / raw)
  To: Jiri Kosina; +Cc: linux-ext4, linux-kernel


'excpet' should be 'except'.
'ext3_get_branch' should be 'ext2_get_branch'.
    
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
---
I found another one.

diff --git a/fs/ext2/inode.c b/fs/ext2/inode.c
index 940c961..533699c 100644
--- a/fs/ext2/inode.c
+++ b/fs/ext2/inode.c
@@ -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
-- 
1.7.2.2


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH UPDATED] ext2: trivial: fix typo on comments in ext2/inode.c
  2010-09-10  1:39 ` [PATCH UPDATED] ext2: trivial: fix typo on comments " Namhyung Kim
@ 2010-09-23 11:50   ` Jiri Kosina
  0 siblings, 0 replies; 3+ messages in thread
From: Jiri Kosina @ 2010-09-23 11:50 UTC (permalink / raw)
  To: Namhyung Kim; +Cc: linux-ext4, linux-kernel

On Fri, 10 Sep 2010, Namhyung Kim wrote:

> 
> 'excpet' should be 'except'.
> 'ext3_get_branch' should be 'ext2_get_branch'.
>     
> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
> ---
> I found another one.
> 
> diff --git a/fs/ext2/inode.c b/fs/ext2/inode.c
> index 940c961..533699c 100644
> --- a/fs/ext2/inode.c
> +++ b/fs/ext2/inode.c
> @@ -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

Applied.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-09-23 11:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-08 16:14 [PATCH] ext2: trivial: fix a typo on comment in ext2/inode.c Namhyung Kim
2010-09-10  1:39 ` [PATCH UPDATED] ext2: trivial: fix typo on comments " Namhyung Kim
2010-09-23 11:50   ` Jiri Kosina

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.