From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, igt-dev@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel-ci/xe-fast-feedback: fixup xe_dma_buf_sync
Date: Mon, 14 Oct 2024 16:42:10 +0200 [thread overview]
Message-ID: <6c287efe-a696-47e0-bd56-0513617fd829@linux.intel.com> (raw)
In-Reply-To: <20241014084710.63569-1-matthew.auld@intel.com>
On 10/14/2024 10:47 AM, Matthew Auld wrote:
> export-dma-buf-once was split into a few different subtests, but we
> missed updating the test list here.
>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/3061
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> tests/intel-ci/xe-fast-feedback.testlist | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tests/intel-ci/xe-fast-feedback.testlist b/tests/intel-ci/xe-fast-feedback.testlist
> index 01b01dcf9..d9fb98aab 100644
> --- a/tests/intel-ci/xe-fast-feedback.testlist
> +++ b/tests/intel-ci/xe-fast-feedback.testlist
> @@ -75,8 +75,10 @@ igt@xe_create@create-massive-size
> igt@xe_debugfs@base
> igt@xe_debugfs@gt
> igt@xe_debugfs@forcewake
> -igt@xe_dma_buf_sync@export-dma-buf-once
> +igt@xe_dma_buf_sync@export-dma-buf-once-write-sync
> igt@xe_dma_buf_sync@export-dma-buf-once-read-sync
> +igt@xe_dma_buf_sync@export-dma-buf-once-read-write-sync
> +igt@xe_dma_buf_sync@export-dma-buf-once-write-read-sync
> igt@xe_evict_ccs@evict-overcommit-simple
> igt@xe_evict_ccs@evict-overcommit-parallel-nofree-samefd
> igt@xe_exec_atomic@basic-dec-all
prev parent reply other threads:[~2024-10-14 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 8:47 [PATCH i-g-t] tests/intel-ci/xe-fast-feedback: fixup xe_dma_buf_sync Matthew Auld
2024-10-14 10:02 ` Kamil Konieczny
2024-10-14 14:42 ` Nirmoy Das [this message]
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=6c287efe-a696-47e0-bd56-0513617fd829@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=nirmoy.das@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox