From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Ramesh Adhikari" <adhikari.resume@gmail.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ LGCI.VerificationFailed: failure for drm/xe: Add bounds check for num_binds to prevent memory exhaustion (rev2)
Date: Thu, 07 May 2026 12:55:05 -0000 [thread overview]
Message-ID: <177815850508.47093.3344374600922104964@5ab824fced77> (raw)
In-Reply-To: <20260506180636.23771-1-adhikari.resume@gmail.com>
== Series Details ==
Series: drm/xe: Add bounds check for num_binds to prevent memory exhaustion (rev2)
URL : https://patchwork.freedesktop.org/series/166134/
State : failure
== Summary ==
Address 'adhikari.resume@gmail.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-05-07 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 18:06 [PATCH] drm/xe: Add bounds check for num_binds to prevent memory exhaustion Ramesh Adhikari
2026-05-06 19:28 ` Matthew Brost
2026-05-07 6:31 ` Thomas Hellström
2026-05-07 6:50 ` Matthew Brost
2026-05-07 12:55 ` 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=177815850508.47093.3344374600922104964@5ab824fced77 \
--to=patchwork@emeril.freedesktop.org \
--cc=adhikari.resume@gmail.com \
--cc=intel-xe@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).