From: Daniel Vetter <daniel@ffwll.ch>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Sourab Gupta <sourab.gupta@intel.com>
Subject: Re: [PATCH i-g-t 1/1] igt/dapc: Test Driver Assisted Performance Capture (DAPC)
Date: Wed, 30 Aug 2017 14:21:13 +0200 [thread overview]
Message-ID: <20170830122113.i4zm4o3ykbqkoy55@phenom.ffwll.local> (raw)
In-Reply-To: <42362bf2-9057-14dc-b853-f1677cb7517d@intel.com>
On Wed, Aug 30, 2017 at 10:43:47AM +0100, Lionel Landwerlin wrote:
> On 30/08/17 10:39, Daniel Vetter wrote:
> > Also dapc is not a good testcase name, needs some proper prefixing.
>
>
> Reminds me perf.c should probably be renamed too.
> What would be an appropriate name? intel_perf.c?
I think at least a common prefix for all the perf related stuff would be
good. Atm we don't have a consistent rule for prefixing intel-specific
tests, so perf and perf_dapc sound ok to me. If you want, add an intel_
prefix for fun.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-30 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 9:53 [PATCH i-g-t 1/1] igt/dapc: Test Driver Assisted Performance Capture (DAPC) Sagar Arun Kamble
2017-08-28 11:51 ` ✗ Fi.CI.BAT: failure for series starting with [1/1] " Patchwork
2017-08-29 8:51 ` [PATCH i-g-t 1/1] " Lionel Landwerlin
2017-08-30 11:17 ` Kamble, Sagar A
2017-08-30 9:39 ` Daniel Vetter
2017-08-30 9:43 ` Lionel Landwerlin
2017-08-30 12:21 ` Daniel Vetter [this message]
2017-08-30 11:04 ` Kamble, Sagar A
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=20170830122113.i4zm4o3ykbqkoy55@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@intel.com \
--cc=sourab.gupta@intel.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 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.