All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Namhyung Kim <namhyung@gmail.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH UPDATED] ext2: trivial: fix typo on comments in ext2/inode.c
Date: Thu, 23 Sep 2010 13:50:58 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1009231350530.26813@pobox.suse.cz> (raw)
In-Reply-To: <87eid2peb2.fsf@gmail.com>

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.

      reply	other threads:[~2010-09-23 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LNX.2.00.1009231350530.26813@pobox.suse.cz \
    --to=jkosina@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.