public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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] befs: fix typos in btree.c
Date: Fri, 12 Aug 2016 08:30:10 +0100	[thread overview]
Message-ID: <20160812073009.GA6693@pc> (raw)
In-Reply-To: <1470950116-30662-1-git-send-email-luisbg@osg.samsung.com>

On Thu, Aug 11, 2016 at 10:15:16PM +0100, Luis de Bethencourt wrote:
> Fixing typos in kernel-doc function descriptions in fs/befs/btree.c.
> 
> Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
> ---
> 
> Hi,
> 
> Noticed the typo of "actuall" below and decided to fix all typos in the
> btree.c file.
> 
> Thanks,
> Luis
> 
>  fs/befs/btree.c | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/befs/btree.c b/fs/befs/btree.c
> index 54a1f95..866d070 100644
> --- a/fs/befs/btree.c
> +++ b/fs/befs/btree.c
> @@ -242,7 +242,7 @@ befs_bt_read_node(struct super_block *sb, const befs_data_stream *ds,
>   *   Read the superblock and rootnode of the b+tree.
>   *   Drill down through the interior nodes using befs_find_key().
>   *   Once at the correct leaf node, use befs_find_key() again to get the
> - *   actuall value stored with the key.
> + *   actual value stored with the key.
>   */
>  int
>  befs_btree_find(struct super_block *sb, const befs_data_stream *ds,
> @@ -397,7 +397,7 @@ befs_find_key(struct super_block *sb, struct befs_btree_node *node,
>   * @keysize: Length of the returned key
>   * @value: Value stored with the returned key
>   *
> - * Heres how it works: Key_no is the index of the key/value pair to 
> + * Here's how it works: Key_no is the index of the key/value pair to
>   * return in keybuf/value.
>   * Bufsize is the size of keybuf (BEFS_NAME_LEN+1 is a good size). Keysize is 
>   * the number of characters in the key (just a convenience).
> @@ -533,7 +533,6 @@ befs_btree_read(struct super_block *sb, const befs_data_stream *ds,
>   * @node_off: Pointer to offset of current node within datastream. Modified
>   * 		by the function.
>   *
> - *
>   * Helper function for btree traverse. Moves the current position to the 
>   * start of the first leaf node.
>   *
> @@ -707,7 +706,7 @@ befs_bt_get_key(struct super_block *sb, struct befs_btree_node *node,
>   *
>   * Returns 0 if @key1 and @key2 are equal.
>   * Returns >0 if @key1 is greater.
> - * Returns <0 if @key2 is greater..
> + * Returns <0 if @key2 is greater.
>   */
>  static int
>  befs_compare_strings(const void *key1, int keylen1,
> -- 
> 2.5.1
> 

Signed-off-by: Salah Triki <salah.triki@gmail.com>

Thanx,
Salah

      reply	other threads:[~2016-08-12  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 21:15 [PATCH] befs: fix typos in btree.c Luis de Bethencourt
2016-08-12  7:30 ` Salah Triki [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=20160812073009.GA6693@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