[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4947c9e9-ec52-c6be-9f81-e341ddac4e54@amd.com>
Date: Fri, 13 May 2022 12:42:02 +0200
From: Christian König <christian.koenig@....com>
To: Charan Teja Kalla <quic_charante@...cinc.com>,
Greg KH <gregkh@...uxfoundation.org>
Cc: sumit.semwal@...aro.org, hridya@...gle.com, daniel.vetter@...ll.ch,
tjmercier@...gle.com, linux-media@...r.kernel.org,
dri-devel@...ts.freedesktop.org, linaro-mm-sig@...ts.linaro.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3] dma-buf: ensure unique directory name for dmabuf stats
Am 13.05.22 um 12:38 schrieb Charan Teja Kalla:
> On 5/13/2022 3:59 PM, Christian König wrote:
>> Am 13.05.22 um 12:18 schrieb Charan Teja Kalla:
>>> On 5/13/2022 3:41 PM, Greg KH wrote:
>>>>> Reported-by: kernel test robot <lkp@...el.com>
>>>> The trest robot did not say that the dmabuf stat name was being
>>>> duplicated, did it?
>>>>
>>> It reported a printk warning on V2[1]. Should we remove this on V3?
>> We only add the kernel test robot is report when it found the underlying
>> problem and not just noted some warning on an intermediate patch version.
> Noted. Thanks!!
>>> @Christian: Could you please drop this tag while merging?
>> Sure, I don't have much on my plate at the moment. But don't let it
>> become a habit.
>>
> Sure. I am also thinking If it is worth to add stable tag? Though it is
> not crashing the kernel but definitely making the dma_buf_export to fail
> for no reason.
>
> If yes, I can resend the patch with all these tags.
Yeah, sure.
Christian.
>
>> Going to push it upstream through drm-misc-fixes now.
Powered by blists - more mailing lists