From: zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org>
To: "Christian König"
<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH 1/2] drm/amdgpu: fix gpu reset crash
Date: Tue, 25 Apr 2017 10:20:07 +0800 [thread overview]
Message-ID: <58FEB257.2010002@amd.com> (raw)
In-Reply-To: <a43a71f9-b8b1-4ff3-3532-d13bdd539761-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
On 2017年04月24日 17:47, Christian König wrote:
>> The root cause is some ring doesn't have scheduler, like KIQ ring
>>
>> Change-Id: I420e84add9cdd9a7fd1f9921b8a5d0afa3dd2058
>> Signed-off-by: Chunming Zhou <David1.Zhou@amd.com>
>
> Reviewed-by: Christian König <christian.koenig@amd.com> for both.
I forgot to add RB when pushing patches, How can I add it again?
Sorry for that.
David Zhou
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-04-25 2:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 9:40 [PATCH 1/2] drm/amdgpu: fix gpu reset crash Chunming Zhou
[not found] ` <1493026850-29604-1-git-send-email-David1.Zhou-5C7GfCeVMHo@public.gmane.org>
2017-04-24 9:40 ` [PATCH 2/2] drm/amdgpu: fix NULL pointer error Chunming Zhou
2017-04-24 9:47 ` [PATCH 1/2] drm/amdgpu: fix gpu reset crash Christian König
[not found] ` <a43a71f9-b8b1-4ff3-3532-d13bdd539761-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-04-25 2:20 ` zhoucm1 [this message]
[not found] ` <58FEB257.2010002-5C7GfCeVMHo@public.gmane.org>
2017-04-25 8:07 ` Christian König
2017-04-25 13:34 ` Deucher, Alexander
[not found] ` <BN6PR12MB1652CAFE2B4D576733D2EBA3F71E0-/b2+HYfkarQqUD6E6FAiowdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-04-26 4:57 ` zhoucm1
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=58FEB257.2010002@amd.com \
--to=david1.zhou-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.