On 5/30/18 1:37 PM, Mike Snitzer wrote: > On Wed, May 30 2018 at 2:55pm -0400, > Jens Axboe <axboe@xxxxxxxxx> wrote: > >> On 5/30/18 7:36 AM, Mike Snitzer wrote: >>> So revisiting this patchset: are you inclined to take these changes (I >>> assume yes)? If so, what would you need in order to get them staged for >>> 4.18? I'll start with offering my review in reply to the DM patch. I'd >>> much prefer to see this level of change go in sooner rather than later. >> >> Yeah I'd like to take the changes, but we might have to wait for >> 4.19 at this point. It'd certainly help to have the dm bits reviewed, >> as they are some of the larger ones. The grunt of the others are mostly >> trivial and smaller in scope. > > I _really_ would like to see this land for 4.18. It'll avoid downstream > backport problems (due to all the churn in this patchset). > > As I'm sure you've seen I reviewed and Acked-by the DM patch. > > I mentioned I've been chatting with Kent, he is available if anything > needs a v2 for whatever reason. > > Would you be OK adding a single sentence description to each driver's > patch header (rather than leaving empty like how Kent submitted)? Or > should Kent resubmit the entire set with that boilerplate header for > each patch? See previous email for both questions :) -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
