On Tue, Mar 07, 2017 at 06:35:02PM +, Filipe Manana wrote:
> On Tue, Mar 7, 2017 at 4:05 PM, David Sterba wrote:
> > On Mon, Mar 06, 2017 at 11:32:47PM +, fdman...@kernel.org wrote:
> >> From: Filipe Manana
> >>
> >> The delalloc_end parameter for extent_clear_unlock_delalloc() is never
>
On Tue, Mar 7, 2017 at 4:05 PM, David Sterba wrote:
> On Mon, Mar 06, 2017 at 11:32:47PM +, fdman...@kernel.org wrote:
>> From: Filipe Manana
>>
>> The delalloc_end parameter for extent_clear_unlock_delalloc() is never
>> used, and only making the code for all callers longer and more complex.
On Mon, Mar 06, 2017 at 11:32:47PM +, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> The delalloc_end parameter for extent_clear_unlock_delalloc() is never
> used, and only making the code for all callers longer and more complex.
> Just remove it.
It's been added on purpose
https://gi
From: Filipe Manana
The delalloc_end parameter for extent_clear_unlock_delalloc() is never
used, and only making the code for all callers longer and more complex.
Just remove it.
Signed-off-by: Filipe Manana
---
fs/btrfs/extent_io.c | 2 +-
fs/btrfs/extent_io.h | 2 +-
fs/btrfs/inode.c |