Re: [PATCH v5 3/8] dma-buf: Always build with DMABUF_MOVE_NOTIFY

["Christian König" <christian.koenig@amd.com>]

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 <leonro@nvidia.com>
>>>
>>> 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 <christian.koenig@amd.com>
>>> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
>>
>> Reviewed-by: Christian König <christian.koenig@amd.com>
>>
>> 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.

Regards,
Christian.

> 
> Thanks
> 
>>
>> They are basically just cleanups we should have done a long time ago.
>>
>> Regards,
>> Christian.
>>