From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Brost" <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] ○ CI.BAT: info for USM locking fixes
Date: Wed, 22 Mar 2023 00:13:27 -0000 [thread overview]
Message-ID: <167944400775.13422.4381264683043135528@emeril.freedesktop.org> (raw)
In-Reply-To: <20230321234217.692726-1-matthew.brost@intel.com>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
== Series Details ==
Series: USM locking fixes
URL : https://patchwork.freedesktop.org/series/115467/
State : info
== Summary ==
Participating hosts:
bat-dg1-8
bat-dg2-oem2
bat-adlp-7
Missing hosts results[1]:
bat-dg1-8
Results: [xe-pw-115467v1](https://intel-gfx-ci.01.org/tree/xe/xe-pw-115467v1/index.html)
[-- Attachment #2: Type: text/html, Size: 832 bytes --]
prev parent reply other threads:[~2023-03-22 0:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 23:42 [Intel-xe] [PATCH 0/2] USM locking fixes Matthew Brost
2023-03-21 23:42 ` [Intel-xe] [PATCH 1/2] drn/xe: Drop usm lock around ASID xarray Matthew Brost
2023-03-24 6:17 ` Niranjana Vishwanathapura
2023-03-24 7:19 ` Matthew Brost
2023-03-21 23:42 ` [Intel-xe] [PATCH 2/2] drm/xe: Move in fault mode / non-fault mode check to xe_vm_create Matthew Brost
2023-03-24 6:10 ` Niranjana Vishwanathapura
2023-03-24 7:20 ` Matthew Brost
2023-03-24 16:25 ` Maarten Lankhorst
2023-03-24 16:27 ` Matthew Brost
2023-03-24 16:24 ` Matthew Brost
2023-03-21 23:44 ` [Intel-xe] ✓ CI.Patch_applied: success for USM locking fixes Patchwork
2023-03-21 23:45 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-21 23:49 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-22 0:13 ` Patchwork [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=167944400775.13422.4381264683043135528@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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.