On Mon, Sep 14, 2026 at 12:09:35PM +0300, Andrey Drobyshev wrote: > On 7/31/26 11:31 AM, Andrey Drobyshev wrote: > > On 7/31/26 2:49 AM, Michael S. Tsirkin wrote: > >> On Fri, Jul 24, 2026 at 02:45:37PM +0300, Andrey Drobyshev wrote: > >>> v5 -> v6: > >>> > >>> * Patch 4: > >>> - make sync+flush conditional by adding a bool 'sync' param to the > >>> chain, as suggested by Michael: > >>> vhost_dev_reset_owner() > >>> vhost_dev_cleanup() > >>> vhost_workers_free() > >>> > >>> - reword commit message and comment; > >>> - drop Fixes; > >>> > >>> * Patch 5: > >>> - add 'sync' param to vhost_dev_reset_owner() call. > >>> > >>> v5: > >>> https://lore.kernel.org/virtualization/[email protected] > >> > >> does not apply for me is this for net next? > >> in that case > >> > >> Acked-by: Michael S. Tsirkin <[email protected]> > >> > > > > The series is based on tag v7.2-rc1. However I think the reason it > > doesn't apply is you already have v5 of this series queued in > > mst/linux-next, commits ddb0918e36c4^..ad5b642c84d0, with your S-o-b. > > > > So you might roll it back and take v6 instead (only commits 4 and 5 > > differ), or leave v5 in the tree, or I can send you v5->v6 difference > > separately. Whichever you prefer. > > Friendly ping. > > I noticed that these patches were queued in your linux-next tree, but > got dropped afterwards and never made it to your last PR (used to be > ddb0918e36c4^..ad5b642c84d0). To be clear: the series targets your > vhost tree, not net-next tree. Since it applies cleanly on your current > vhost branch - please let me know if it's ready or there's smth else > that should be fixed. > > Thanks, > Andrey
I'll put this in next, thanks!
