[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e94363a-b449-4efb-b2fe-c1dd710b57c9@amd.com>
Date: Mon, 1 Apr 2024 14:45:40 +0200
From: Christian König <christian.koenig@....com>
To: Tvrtko Ursulin <tursulin@...ulin.net>, "T.J. Mercier"
<tjmercier@...gle.com>, Tvrtko Ursulin <tursulin@...lia.com>
Cc: dri-devel@...ts.freedesktop.org, Sumit Semwal <sumit.semwal@...aro.org>,
linux-media@...r.kernel.org, linaro-mm-sig@...ts.linaro.org,
linux-kernel@...r.kernel.org, kernel-dev@...lia.com
Subject: Re: [PATCH] dma-buf: Do not build debugfs related code when
!CONFIG_DEBUG_FS
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@...lia.com>
>> wrote:
>>>
>>> From: Tvrtko Ursulin <tursulin@...ulin.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@...ulin.net>
>>
>> Reviewed-by: T.J. Mercier <tjmercier@...gle.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@....com> as well.
Regards,
Christian.
>
> Regards,
>
> Tvrtko
Powered by blists - more mailing lists