Re: [PATCH 1/3] befs: fix typos in datastream.c

[Salah Triki <salah.triki@gmail.com>]

On Sat, Aug 13, 2016 at 06:11:19PM +0100, Luis de Bethencourt wrote:
> Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
> ---
> 
> Hi,
> 
> This is a series of patches fixing small issues in datastream.c.
> 
> On the process of doing the same for the rest of files. To finish cleanup
> and start adding documentation and new features.
> 
> Thanks,
> Luis
> 
>  fs/befs/datastream.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/befs/datastream.c b/fs/befs/datastream.c
> index 6889644..b2eb5b5 100644
> --- a/fs/befs/datastream.c
> +++ b/fs/befs/datastream.c
> @@ -37,7 +37,7 @@ static int befs_find_brun_dblindirect(struct super_block *sb,
>  /**
>   * befs_read_datastream - get buffer_head containing data, starting from pos.
>   * @sb: Filesystem superblock
> - * @ds: datastrem to find data with
> + * @ds: datastream to find data with
>   * @pos: start of data
>   * @off: offset of data in buffer_head->b_data
>   *
> @@ -115,7 +115,7 @@ befs_fblock2brun(struct super_block *sb, const befs_data_stream *data,
>  /**
>   * befs_read_lsmylink - read long symlink from datastream.
>   * @sb: Filesystem superblock 
> - * @ds: Datastrem to read from
> + * @ds: Datastream to read from
>   * @buff: Buffer in which to place long symlink data
>   * @len: Length of the long symlink in bytes
>   *
> @@ -183,7 +183,7 @@ befs_count_blocks(struct super_block *sb, const befs_data_stream *ds)
>  		metablocks += ds->indirect.len;
>  
>  	/*
> -	   Double indir block, plus all the indirect blocks it mapps
> +	   Double indir block, plus all the indirect blocks it maps.
>  	   In the double-indirect range, all block runs of data are
>  	   BEFS_DBLINDIR_BRUN_LEN blocks long. Therefore, we know 
>  	   how many data block runs are in the double-indirect region,
> @@ -397,7 +397,7 @@ befs_find_brun_indirect(struct super_block *sb,
>  	though the double-indirect run may be several blocks long, 
>  	we can calculate which of those blocks will contain the index
>  	we are after and only read that one. We then follow it to 
> -	the indirect block and perform a  similar process to find
> +	the indirect block and perform a similar process to find
>  	the actual block run that maps the data block we are interested
>  	in.
>  	
> -- 
> 2.5.1
> 

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

Thanks,
Salah