btrfs: Fix a typo
PATCH 1/1 btrfs: Fix a typo
s/reponsible/responsible/
--- fs/btrfs/scrub.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/btrfs/scrub.c +1 -1
@@ -2426,7 +2426,7 @@ static void drop_csum_range(struct scrub_ctx *sctx, struct btrfs_ordered_sum *su* the csum into @csum. * * The search source is sctx->csum_list, which is a pre-populated list -* storing bytenr ordered csum ranges. We're reponsible to cleanup any range +* storing bytenr ordered csum ranges. We're responsible to cleanup any range * that is before @logical. * * Return 0 if there is no csum for the range.
--
2.26.2
Quoted 13 lines · Bhaskar Chowdhury
s/reponsible/responsible/
Signed-off-by Bhaskar Chowdhury <[email protected]>--- fs/btrfs/scrub.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)fs/btrfs/scrub.c +0
-0
fs/btrfs/scrub.c static void drop_csum_range(struct scrub_ctx *sctx, struct btrfs_ordered_sum *su · line 2429
Quoted 5 lines
fs/btrfs/scrub.c +1
-1@@ -2426,7 +2426,7 @@ static void drop_csum_range(struct scrub_ctx *sctx, struct btrfs_ordered_sum *su* the csum into @csum. * * The search source is sctx->csum_list, which is a pre-populated list -* storing bytenr ordered csum ranges. We're reponsible to cleanup any range +* storing bytenr ordered csum ranges. We're responsible to cleanup any range
If you are at fixing typos, you may as well fix the grammar at the same time :)
We're responsible to cleanup... -> We're responsible for cleaning up...
Quoted 7 lines
fs/btrfs/scrub.c +0
-1* that is before @logical. * * Return 0 if there is no csum for the range. -- 2.26.2
Signature · 2 lines
Damien Le Moal Western Digital Research
Quoted 2 lines · Bhaskar Chowdhury
s/reponsible/responsible/
So this is exactly what I don't want to see happen - one patch per typo. I tried to explain it in the previous patch, please either fix all typos under fs/btrfs or don't bother.
Quoted 7 lines · David Sterba
Quoted 2 lines · Bhaskar Chowdhury
s/reponsible/responsible/
So this is exactly what I don't want to see happen - one patch per typo. I tried to explain it in the previous patch, please either fix all typos under fs/btrfs or don't bother.
As I mentioned in my previous correspondence to , I have my way of doing thing . The problem is , you are getting accustomed with some specific method and you are thinking that is the "only way" of doing the "right thing" . Please , think others are also think in different way too.
The goal to make it looks good and productive...don't you think so???
..and I said I do bother ,it's just not about this specific segment but about the whole kernel.
Or is it some sort of special flow brtfs subsystem are following , which I am not aware off??
Please do let me.