On Thu, Oct 04, 2018 at 11:26:36AM -0700, Omar Sandoval wrote: > On Mon, Oct 01, 2018 at 05:46:16PM +0300, Nikolay Borisov wrote: > > To help implement free space tree checker in user space some kernel > > function are necessary, namely iterating/deleting/adding freespace > > items, some internal search functions. Functions to populate a block > > group based on the extent tree. The code is largely copy/paste from > > the kernel with locking eliminated (i.e free_space_lock). It supports > > reading/writing of both bitmap and extent based FST trees. > > For some reason, a lot of this added code uses spaces instead of tabs, > so I had to fix that in order to compare it to the kernel code (some of > the functions were reordered, too).
That for noticing it, fixing whitespace damage on 300 lines makes me really annoyed even if vim is a great help here. Patch applied but I'm not doing that next time.
