From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Rodrigo Vivi" <rodrigo.vivi@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] ○ CI.BAT: info for Start killing xe_macros.
Date: Tue, 28 Mar 2023 16:43:28 -0000 [thread overview]
Message-ID: <168002180891.29057.18223474050607928566@emeril.freedesktop.org> (raw)
In-Reply-To: <20230328161021.669017-1-rodrigo.vivi@intel.com>
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
== Series Details ==
Series: Start killing xe_macros.
URL : https://patchwork.freedesktop.org/series/115740/
State : info
== Summary ==
Participating hosts:
bat-atsm-2
bat-dg2-oem2
bat-adlp-7
Missing hosts results[0]:
Results: [xe-pw-115740v1](https://intel-gfx-ci.01.org/tree/xe/xe-pw-115740v1/index.html)
[-- Attachment #2: Type: text/html, Size: 824 bytes --]
prev parent reply other threads:[~2023-03-28 16:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 16:10 [Intel-xe] [RFC 0/5] Start killing xe_macros Rodrigo Vivi
2023-03-28 16:10 ` [Intel-xe] [RFC 1/5] !fixup: drm/i915/display: Remaining changes to make xe compile Rodrigo Vivi
2023-03-28 16:10 ` [Intel-xe] [RFC 2/5] !fixup: drm/xe: Allow fbdev to allocate stolen memory Rodrigo Vivi
2023-03-28 16:10 ` [Intel-xe] [RFC 3/5] drm/xe: Remove useless XE_WARN_ON Rodrigo Vivi
2023-03-28 18:26 ` Matthew Brost
2023-03-28 18:58 ` Rodrigo Vivi
2023-03-28 16:10 ` [Intel-xe] [RFC 4/5] drm/xe: Remove useless XE_BUG_ON Rodrigo Vivi
2023-03-28 20:24 ` Matt Roper
2023-03-28 20:27 ` Vivi, Rodrigo
2023-03-28 21:03 ` Michal Wajdeczko
2023-03-29 9:31 ` Jani Nikula
2023-03-29 19:25 ` Rodrigo Vivi
2023-03-28 16:10 ` [Intel-xe] [RFC 5/5] drm/xe/xe_macro: Remove unused stuff Rodrigo Vivi
2023-03-28 16:16 ` [Intel-xe] ✓ CI.Patch_applied: success for Start killing xe_macros Patchwork
2023-03-28 16:17 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-28 16:21 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-28 16:43 ` 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=168002180891.29057.18223474050607928566@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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.