From: zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org>
To: Andres Rodriguez
<andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org
Subject: Re: [PATCH] More amdgpu trace patches
Date: Fri, 10 Mar 2017 10:51:31 +0800 [thread overview]
Message-ID: <58C214B3.5040608@amd.com> (raw)
In-Reply-To: <20170310022554.4509-1-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
nice patches, the set is Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
On 2017年03月10日 10:25, Andres Rodriguez wrote:
> These are some of the extra changes Christian was requesting in the
> previous ftrace thread.
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-03-10 2:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 2:25 [PATCH] More amdgpu trace patches Andres Rodriguez
[not found] ` <20170310022554.4509-1-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-10 2:25 ` [PATCH 1/5] drm/amd/sched: add a unique job id to amd_sched_job Andres Rodriguez
2017-03-10 2:25 ` [PATCH 2/5] drm/amdgpu: more ftrace formatting consistency fixes Andres Rodriguez
2017-03-10 2:25 ` [PATCH 3/5] drm/amdgpu: use sched_job id instead of pointer for tracing Andres Rodriguez
2017-03-10 2:25 ` [PATCH 4/5] drm/amdgpu: remove useless pointers from traces Andres Rodriguez
2017-03-10 2:25 ` [PATCH 5/5] drm/amdgpu: replace fence pointer with fence data in traces Andres Rodriguez
2017-03-10 2:51 ` zhoucm1 [this message]
[not found] ` <58C214B3.5040608-5C7GfCeVMHo@public.gmane.org>
2017-03-10 9:28 ` [PATCH] More amdgpu trace patches 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=58C214B3.5040608@amd.com \
--to=david1.zhou-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=andresx7-Re5JQEeQqe8AvxtiuMwx3w@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.