All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: arun.r.murthy@intel.com, Jeevan B <jeevan.b@intel.com>
Subject: [PATCH i-g-t 0/3] RFC: Add tests for atomic failure error reporting
Date: Thu,  9 Apr 2026 15:06:36 +0530	[thread overview]
Message-ID: <20260409093639.27449-1-jeevan.b@intel.com> (raw)

RFC IGT patch adding a test for DRM atomic failure error reporting.
This is related to and depends on the KMD series at
https://patchwork.freedesktop.org/series/152276/

Signed-off-by: Jeevan B <jeevan.b@intel.com>

Jeevan B (3):
  DONT_MERGE: include/drm-uapi: Add atomic_ioctl error codes
  DONT_MERGE: include/drm-uapi: Add ERROR_REPORTING capability
  RFC: tests/kms_atomic_error_code: Add tests for atomic failure
    reporting

 include/drm-uapi/drm.h      |   8 ++
 include/drm-uapi/drm_mode.h |  60 ++++++++++++++
 tests/kms_atomic_error.c    | 156 ++++++++++++++++++++++++++++++++++++
 tests/meson.build           |   1 +
 4 files changed, 225 insertions(+)
 create mode 100644 tests/kms_atomic_error.c

-- 
2.43.0


             reply	other threads:[~2026-04-09  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09  9:36 Jeevan B [this message]
2026-04-09  9:36 ` [PATCH i-g-t 1/3] DONT_MERGE: include/drm-uapi: Add atomic_ioctl error codes Jeevan B
2026-04-09  9:36 ` [PATCH i-g-t 2/3] DONT_MERGE: include/drm-uapi: Add ERROR_REPORTING capability Jeevan B
2026-04-09  9:36 ` [PATCH i-g-t 3/3] RFC: tests/kms_atomic_error_code: Add tests for atomic failure reporting Jeevan B
2026-04-10  2:49 ` ✓ i915.CI.BAT: success for RFC: Add tests for atomic failure error reporting Patchwork
2026-04-10  2:50 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-10  6:48 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-10 21:50 ` ✗ i915.CI.Full: " Patchwork

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=20260409093639.27449-1-jeevan.b@intel.com \
    --to=jeevan.b@intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=igt-dev@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 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.