Hi, I'm looking how well does this patchset merges with the rest, so far there are excpected conflicts with Chandan's subpage-blocksize patchset. For the easy parts, we can add stub patches to extend functions like cow_file_range with parameters that are added by the other patch.
Honestly I don't know which patchset to take first. As the subpage-blockszie is in the core, there are no user visibility and interface questions, but it must not cause any regressions. Dedupe is optional, not default, and we have to mainly make sure it does not have any impact when turned off. So I see three possible ways: * merge subpage first, as it defines the API, adapt dedupe * merge dedupe first, as it only enhanced existing API, adapt subpage * create a common branch for both, merge relevant parts of each patchset, add more patches to prepare common ground for either patch You can deduce yourself which vairant poses work on who. My preference is to do the 3rd variant, as it does not force us any particular merge order. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
