[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7328189c-0567-847e-17e9-e2ed4f3a78f4@amd.com>
Date: Mon, 25 Oct 2021 12:58:50 +0200
From: Christian König <christian.koenig@....com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sumit Semwal <sumit.semwal@...aro.org>,
Alex Deucher <alexander.deucher@....com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>, Xinhui.Pan@....com
Cc: linux-kernel@...r.kernel.org,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
dri-devel@...ts.freedesktop.org,
Daniel Vetter <daniel.vetter@...ll.ch>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v2] dma-buf: move dma-buf symbols into the DMA_BUF module
namespace
Am 25.10.21 um 12:36 schrieb Greg Kroah-Hartman:
> On Sun, Oct 10, 2021 at 02:46:28PM +0200, Greg Kroah-Hartman wrote:
>> In order to better track where in the kernel the dma-buf code is used,
>> put the symbols in the namespace DMA_BUF and modify all users of the
>> symbols to properly import the namespace to not break the build at the
>> same time.
>>
>> Now the output of modinfo shows the use of these symbols, making it
>> easier to watch for users over time:
>>
>> $ modinfo drivers/misc/fastrpc.ko | grep import
>> import_ns: DMA_BUF
>>
>> Cc: "Pan, Xinhui" <Xinhui.Pan@....com>
>> Cc: David Airlie <airlied@...ux.ie>
>> Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>
>> Cc: Maxime Ripard <mripard@...nel.org>
>> Cc: Thomas Zimmermann <tzimmermann@...e.de>
>> Cc: Mauro Carvalho Chehab <mchehab@...nel.org>
>> Cc: dri-devel@...ts.freedesktop.org
>> Acked-by: Daniel Vetter <daniel.vetter@...ll.ch>
>> Acked-by: Christian König <christian.koenig@....com>
>> Acked-by: Arnd Bergmann <arnd@...db.de>
>> Acked-by: Sumit Semwal <sumit.semwal@...aro.org>
>> Acked-by: Alex Deucher <alexander.deucher@....com>
>> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> ---
>> v2: added lots of acks
>> added 2 more drivers that needed the change, as found by Arnd
> Ping? Any ideas on what needs to happen to get this into the tree?
>
> Or can I take it through my char-misc tree? I seem to have a bunch of
> acks on it by the respective maintainers...
I could push that upstream through the drm-misc-next tree if you like,
but honestly char-misc sounds like the better approach since this
touches a lot of drivers outside of drm as well.
Thanks,
Christian.
>
> thanks,
>
> greg k-h
Powered by blists - more mailing lists