From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
To: "Christian König" <christian.koenig@amd.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"T.J. Mercier" <tjmercier@google.com>,
"Tvrtko Ursulin" <tursulin@igalia.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
linux-kernel@vger.kernel.org, kernel-dev@igalia.com
Subject: Re: [PATCH] dma-buf: Do not build debugfs related code when !CONFIG_DEBUG_FS
Date: Mon, 1 Apr 2024 14:21:19 +0100 [thread overview]
Message-ID: <4342d02c-a180-4a7e-8ef6-4ece51aba946@igalia.com> (raw)
In-Reply-To: <1e94363a-b449-4efb-b2fe-c1dd710b57c9@amd.com>
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?
Regards,
Tvrtko
next prev parent reply other threads:[~2024-04-01 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 14:53 [PATCH] dma-buf: Do not build debugfs related code when !CONFIG_DEBUG_FS Tvrtko Ursulin
2024-03-29 0:00 ` T.J. Mercier
2024-04-01 12:39 ` Tvrtko Ursulin
2024-04-01 12:45 ` Christian König
2024-04-01 13:21 ` Tvrtko Ursulin [this message]
2024-04-15 17:08 ` Maíra Canal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4342d02c-a180-4a7e-8ef6-4ece51aba946@igalia.com \
--to=tvrtko.ursulin@igalia.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.com \
--cc=tursulin@igalia.com \
--cc=tursulin@ursulin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox