befs: fix typos in datastream.c

Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
Signed-off-by: Salah Triki <salah.triki@gmail.com>
This commit is contained in:
Luis de Bethencourt 2016-08-13 18:11:19 +01:00
parent 02d91f97fd
commit d327e612bd
1 changed files with 4 additions and 4 deletions

View File

@ -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. * befs_read_datastream - get buffer_head containing data, starting from pos.
* @sb: Filesystem superblock * @sb: Filesystem superblock
* @ds: datastrem to find data with * @ds: datastream to find data with
* @pos: start of data * @pos: start of data
* @off: offset of data in buffer_head->b_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. * befs_read_lsmylink - read long symlink from datastream.
* @sb: Filesystem superblock * @sb: Filesystem superblock
* @ds: Datastrem to read from * @ds: Datastream to read from
* @buff: Buffer in which to place long symlink data * @buff: Buffer in which to place long symlink data
* @len: Length of the long symlink in bytes * @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; 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 In the double-indirect range, all block runs of data are
BEFS_DBLINDIR_BRUN_LEN blocks long. Therefore, we know BEFS_DBLINDIR_BRUN_LEN blocks long. Therefore, we know
how many data block runs are in the double-indirect region, 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, though the double-indirect run may be several blocks long,
we can calculate which of those blocks will contain the index we can calculate which of those blocks will contain the index
we are after and only read that one. We then follow it to 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 the actual block run that maps the data block we are interested
in. in.