[WIP] [NOMERGE] [RFC PATCH v0.3 3/6] erofs: introduce erofs_map_blocks_iter

[Gao Xiang]

Hi Chao,

On 2018/7/2 11:36, Chao Yu wrote:
> We can do both of them, let's treat erofs branch as master branch, and we can
> split erofs-dev branch (dev-test will not be so obvious to indicate that branch
> is belong to erofs, so let's use erofs-dev) from erofs branch for further
> development.
> 
> So in erofs-dev, we can do anything temporarily change and testing, and once it
> becomes stable, we can merge there-in patches back to erofs branch.
> 
> And for any old codes or implementation obsolescing in erofs branch, let's use
> git-revert or remove codes in a separated patch instead of dropping a patch
> directly. :)
> 
> How do you think?

*nod* *nod* *nod*, this policy is fine with me :)

and for these backport branches, I try to stablize the new unzip subsystem this week...

and then we could start to begin backport and the whole fs bugfix work,
eg. starting from seperate and discard these confusing LINUX_VERSION marcos...

Thanks,

> 
> Thanks,