linux-kernel - Re: [PATCH] dma-buf: Do not build debugfs related code when !CONFIG_DEBUG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4342d02c-a180-4a7e-8ef6-4ece51aba946@igalia.com>
Date: Mon, 1 Apr 2024 14:21:19 +0100
From: Tvrtko Ursulin <tvrtko.ursulin@...lia.com>
To: Christian König <christian.koenig@....com>,
 Tvrtko Ursulin <tursulin@...ulin.net>, "T.J. Mercier"
 <tjmercier@...gle.com>, Tvrtko Ursulin <tursulin@...lia.com>,
 Maarten Lankhorst <maarten.lankhorst@...ux.intel.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

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@...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.

Thanks!

Maarten if I got it right you are handling the next drm-misc-next pull - 
could you merge this one please?

Regards,

Tvrtko