From: Charan Teja Kalla <quic_charante@quicinc.com>
To: "Christian König" <christian.koenig@amd.com>,
"Greg KH" <gregkh@linuxfoundation.org>
Cc: <sumit.semwal@linaro.org>, <hridya@google.com>,
<daniel.vetter@ffwll.ch>, <tjmercier@google.com>,
<linux-media@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linaro-mm-sig@lists.linaro.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] dma-buf: ensure unique directory name for dmabuf stats
Date: Fri, 13 May 2022 16:08:51 +0530 [thread overview]
Message-ID: <f5988884-ba0a-643c-e920-6ae626bb67a1@quicinc.com> (raw)
In-Reply-To: <0071e117-1d91-b086-7cb1-976b2a1c3498@amd.com>
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@intel.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.
> Going to push it upstream through drm-misc-fixes now.
next prev parent reply other threads:[~2022-05-13 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 9:38 Charan Teja Kalla
2022-05-13 10:11 ` Greg KH
2022-05-13 10:18 ` Charan Teja Kalla
2022-05-13 10:26 ` Greg KH
2022-05-13 10:29 ` Christian König
2022-05-13 10:38 ` Charan Teja Kalla [this message]
2022-05-13 10:42 ` Christian König
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=f5988884-ba0a-643c-e920-6ae626bb67a1@quicinc.com \
--to=quic_charante@quicinc.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hridya@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.com \
/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
all inboxes | Powered by JetHome®