From: Matthew Auld <matthew.auld@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] benchmarks: Drop gem_mmap
Date: Tue, 4 Feb 2020 16:46:33 +0000 [thread overview]
Message-ID: <3241d683-2e7c-0cd8-1c4e-7bb88fabde02@intel.com> (raw)
In-Reply-To: <20200204162732.1299743-1-chris@chris-wilson.co.uk>
On 04/02/2020 16:27, Chris Wilson wrote:
> Read/write access speed is covered by
> i915_selftests/perf_memory_regions.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-04 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 16:27 [igt-dev] [PATCH i-g-t] benchmarks: Drop gem_mmap Chris Wilson
2020-02-04 16:46 ` Matthew Auld [this message]
2020-02-04 17:10 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-06 16:59 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=3241d683-2e7c-0cd8-1c4e-7bb88fabde02@intel.com \
--to=matthew.auld@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox