From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: "Christian König" <christian.koenig@amd.com>,
jie1zhan <jesse.zhang@amd.com>,
broonie@kernel.org, alsa-devel@alsa-project.org
Cc: Sunil-kumar.Dommati@amd.com, Daniel Vetter <daniel@ffwll.ch>,
ajitkumar.pandey@amd.com, David Airlie <airlied@linux.ie>,
Basavaraj.Hiregoudar@amd.com,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
open list <linux-kernel@vger.kernel.org>,
Maxime Ripard <mripard@kernel.org>,
"moderated list:DMA BUFFER SHARING FRAMEWORK"
<linaro-mm-sig@lists.linaro.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Vijendar.Mukunda@amd.com, Sumit Semwal <sumit.semwal@linaro.org>,
"open list:DMA BUFFER SHARING FRAMEWORK"
<linux-media@vger.kernel.org>
Subject: Re: [PATCH v1] Fix: SYNCOBJ TIMELINE Test failed.
Date: Thu, 30 Jun 2022 09:01:47 +0200 [thread overview]
Message-ID: <83341d51-6c63-4b37-2f02-b3f305930308@linux.intel.com> (raw)
In-Reply-To: <8499b1f1-cd39-5cb4-9fac-735e68393556@amd.com>
On 6/29/2022 11:12 AM, Christian König wrote:
> Am 29.06.22 um 08:02 schrieb jie1zhan:
>> The issue cause by the commit :
>>
>> 721255b527(drm/syncobj: flatten dma_fence_chains on transfer).
>>
>> Because it use the point of dma_fence incorrectly
>>
>> Correct the point of dma_fence by fence array
>
> Well that patch is just utterly nonsense as far as I can see.
>
>>
>> Signed-off-by: jie1zhan <jesse.zhang@amd.com>
>>
>> Reviewed-by: Christian König <christian.koenig@amd.com>
>>
>> Reviewed-by: Nirmoy Das <nirmoy.das@linux.intel.com>
>
> I have strong doubts that Nirmoy has reviewed this and I certainly
> haven't reviewed it.
I haven't reviewed this either.
Nirmoy
>
> Christian.
>
>> ---
>> drivers/gpu/drm/drm_syncobj.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/drm_syncobj.c
>> b/drivers/gpu/drm/drm_syncobj.c
>> index 7e48dcd1bee4..d5db818f1c76 100644
>> --- a/drivers/gpu/drm/drm_syncobj.c
>> +++ b/drivers/gpu/drm/drm_syncobj.c
>> @@ -887,7 +887,7 @@ static int drm_syncobj_flatten_chain(struct
>> dma_fence **f)
>> goto free_fences;
>> dma_fence_put(*f);
>> - *f = &array->base;
>> + *f = array->fences[0];
>> return 0;
>> free_fences:
>
next prev parent reply other threads:[~2022-07-04 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220629060236.3283445-1-jesse.zhang@amd.com>
2022-06-29 9:12 ` [PATCH v1] Fix: SYNCOBJ TIMELINE Test failed Christian König
2022-06-30 7:01 ` Das, Nirmoy [this message]
2022-06-30 15:26 ` Zhang, Jesse(Jie)
2022-06-30 15:41 ` 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=83341d51-6c63-4b37-2f02-b3f305930308@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=airlied@linux.ie \
--cc=ajitkumar.pandey@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesse.zhang@amd.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=mripard@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
/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