On Tue, Jan 27, 2026 at 11:02:03AM +0100, Christian König wrote: > On 1/27/26 10:58, Leon Romanovsky wrote: > > On Tue, Jan 27, 2026 at 10:26:26AM +0100, Christian König wrote: > >> On 1/24/26 20:14, Leon Romanovsky wrote: > >>> From: Leon Romanovsky <[email protected]> > >>> > >>> DMABUF_MOVE_NOTIFY was introduced in 2018 and has been marked as > >>> experimental and disabled by default ever since. Six years later, > >>> all new importers implement this callback. > >>> > >>> It is therefore reasonable to drop CONFIG_DMABUF_MOVE_NOTIFY and > >>> always build DMABUF with support for it enabled. > >>> > >>> Suggested-by: Christian König <[email protected]> > >>> Signed-off-by: Leon Romanovsky <[email protected]> > >> > >> Reviewed-by: Christian König <[email protected]> > >> > >> As long as nobody starts screaming in the last second or I encounter some > >> other problem I'm going to push the first three patches to drm-misc-next > >> now. > > > > How do you see progress of other patches? > > Can they be queued for that tree as well? > > I was hoping to get through them by the end of the week. > > Just wanted to make sure that CI systems start to see the first three patches > (who affect everybody), so that we get early feedback should we have missed > something.
Perfect, I based my patches on these two commits: 61ceaf236115 (vfio/for-linus) vfio: Prevent from pinned DMABUF importers to attach to VFIO DMABUF 24d479d26b25 (tag: v6.19-rc6) Linux 6.19-rc6 Thanks > > Regards, > Christian. > > > > > Thanks > > > >> > >> They are basically just cleanups we should have done a long time ago. > >> > >> Regards, > >> Christian. > >> >
