On 2022-09-23 00:01, Christoph Hellwig wrote: > Thanks, the entire series looks good to me now: > > Reviewed-by: Christoph Hellwig <hch@xxxxxx> > > Given that this is spread all over, what tree do we want to take it > through? Yes, while this is ostensibly a feature for NVMe it turns out we didn't need to touch any NVMe code at all. The most likely patch in my mind to have conflicts is the iov_iter patch as there's been a lot of churn there in the last few cycles and there are continued discussions. There are 2 PCI patches, but Bjorn's aware of them and has acked them. I'm also fairly confident this shouldn't conflict with anything in his tree. Besides that, there is one mm/gup patch which is the next likely to conflict; one scatterlist patch and three block layer patches which have largely been stable when I've done rebases. Logan
