From: Salah Triki <salah.triki@gmail.com>
To: Luis de Bethencourt <luisbg@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
viro@zeniv.linux.org.uk, salah.triki@acm.org
Subject: Re: [PATCH v2 2/2] befs: fix typo in befs_find_key
Date: Sat, 6 Aug 2016 19:40:04 +0100 [thread overview]
Message-ID: <20160806184004.GE3423@pc> (raw)
In-Reply-To: <1470400881-1348-2-git-send-email-luisbg@osg.samsung.com>
On Fri, Aug 05, 2016 at 01:41:21PM +0100, Luis de Bethencourt wrote:
> Fixing skeep to skip.
>
> Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
> ---
> fs/befs/btree.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/befs/btree.c b/fs/befs/btree.c
> index bc7efb0..784688c 100644
> --- a/fs/befs/btree.c
> +++ b/fs/befs/btree.c
> @@ -343,7 +343,7 @@ befs_find_key(struct super_block *sb, struct befs_btree_node *node,
>
> findkey_len = strlen(findkey);
>
> - /* if node can not contain key, just skeep this node */
> + /* if node can not contain key, just skip this node */
> last = node->head.all_key_count - 1;
> thiskey = befs_bt_get_key(sb, node, last, &keylen);
>
> --
> 2.5.1
>
Ack-by: Salah Triki <salah.triki@gmail.com>
Thanx Luis :)
Salah
next prev parent reply other threads:[~2016-08-06 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 12:41 [PATCH v2 1/2] befs: remove unused BEFS_BT_MATCH Luis de Bethencourt
2016-08-05 12:41 ` [PATCH v2 2/2] befs: fix typo in befs_find_key Luis de Bethencourt
2016-08-06 18:40 ` Salah Triki [this message]
2016-08-06 18:34 ` [PATCH v2 1/2] befs: remove unused BEFS_BT_MATCH Salah Triki
2016-08-06 18:44 ` Luis de Bethencourt
2016-08-08 14:21 ` [PATCH v3 1/2] befs: remove unused BEFS_BT_PARMATCH Luis de Bethencourt
2016-08-08 14:21 ` [PATCH v3 2/2] befs: fix typo in befs_find_key Luis de Bethencourt
2016-08-09 12:40 ` [PATCH v3 1/2] befs: remove unused BEFS_BT_PARMATCH Salah Triki
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=20160806184004.GE3423@pc \
--to=salah.triki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--cc=salah.triki@acm.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox