From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ LGCI.VerificationFailed: failure for drm/xe: Don't use UTS_RELEASE directly
Date: Thu, 30 Apr 2026 19:00:17 -0000 [thread overview]
Message-ID: <177757561750.28202.8143830669970927863@5ab824fced77> (raw)
In-Reply-To: <20260428102527.189593-2-u.kleine-koenig@baylibre.com>
== Series Details ==
Series: drm/xe: Don't use UTS_RELEASE directly
URL : https://patchwork.freedesktop.org/series/165799/
State : failure
== Summary ==
Address 'u.kleine-koenig@baylibre.com' is not on the allowlist, which prevents CI from being triggered for this patch.
If you want Intel GFX CI to accept this address, please contact the script maintainers at i915-ci-infra@lists.freedesktop.org.
Exception occurred during validation, bailing out!
prev parent reply other threads:[~2026-04-30 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 10:25 [PATCH v2] drm/xe: Don't use UTS_RELEASE directly Uwe Kleine-König (The Capable Hub)
2026-04-28 11:09 ` Jani Nikula
2026-04-28 13:32 ` Uwe Kleine-König (The Capable Hub)
2026-04-28 19:58 ` Rodrigo Vivi
2026-04-28 20:01 ` Souza, Jose
2026-04-28 20:21 ` Rodrigo Vivi
2026-04-30 19:00 ` 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=177757561750.28202.8143830669970927863@5ab824fced77 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=u.kleine-koenig@baylibre.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).