[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linaro-mm-sig
Subject:    [Linaro-mm-sig] Re: [PATCH] dma-buf: Do not build debugfs related code when !CONFIG_DEBUG_FS
From:       Maíra_Canal <mcanal () igalia ! com>
Date:       2024-04-15 17:08:47
Message-ID: cb5dbffc-98d7-41e9-8a08-774d1f575b29 () igalia ! com
[Download RAW message or body]

Hi Tvrtko,

On 4/1/24 10:21, Tvrtko Ursulin wrote:
> 
> On 01/04/2024 13:45, Christian König wrote:
>> Am 01.04.24 um 14:39 schrieb Tvrtko Ursulin:
>>>
>>> On 29/03/2024 00:00, T.J. Mercier wrote:
>>>> On Thu, Mar 28, 2024 at 7:53 AM Tvrtko Ursulin <tursulin@igalia.com> 
>>>> wrote:
>>>>>
>>>>> From: Tvrtko Ursulin <tursulin@ursulin.net>
>>>>>
>>>>> There is no point in compiling in the list and mutex operations 
>>>>> which are
>>>>> only used from the dma-buf debugfs code, if debugfs is not compiled 
>>>>> in.
>>>>>
>>>>> Put the code in questions behind some kconfig guards and so save 
>>>>> some text
>>>>> and maybe even a pointer per object at runtime when not enabled.
>>>>>
>>>>> Signed-off-by: Tvrtko Ursulin <tursulin@ursulin.net>
>>>>
>>>> Reviewed-by: T.J. Mercier <tjmercier@google.com>
>>>
>>> Thanks!
>>>
>>> How would patches to dma-buf be typically landed? Via what tree I 
>>> mean? drm-misc-next?
>>
>> That should go through drm-misc-next.
>>
>> And feel free to add Reviewed-by: Christian König 
>> <christian.koenig@amd.com> as well.
> 
> Thanks!
> 
> Maarten if I got it right you are handling the next drm-misc-next pull - 
> could you merge this one please?

Applied to drm-misc/drm-misc-next!

Best Regards,
- Maíra

> 
> Regards,
> 
> Tvrtko
_______________________________________________
Linaro-mm-sig mailing list -- linaro-mm-sig@lists.linaro.org
To unsubscribe send an email to linaro-mm-sig-leave@lists.linaro.org

[prev in list] [next in list] [prev in thread] [next in thread]