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] [day] [month] [year] [list]
Message-ID: <cb5dbffc-98d7-41e9-8a08-774d1f575b29@igalia.com>
Date: Mon, 15 Apr 2024 14:08:47 -0300
From: Maíra Canal <mcanal@...lia.com>
To: Tvrtko Ursulin <tvrtko.ursulin@...lia.com>,
 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

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

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

Best Regards,
- Maíra

> 
> Regards,
> 
> Tvrtko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ