All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Summers <stuart.summers@intel.com>
Cc: igt-dev@lists.freedesktop.org, rodrigo.vivi@intel.com,
	matthew.brost@intel.com, umesh.nerlige.ramappa@intel.com,
	Michal.Wajdeczko@intel.com, matthew.d.roper@intel.com,
	daniele.ceraolospurio@intel.com, shuicheng.lin@intel.com,
	Stuart Summers <stuart.summers@intel.com>
Subject: [PATCH i-g-t 0/2] Test new debug based configfs changes
Date: Fri, 21 Aug 2026 19:23:31 +0000	[thread overview]
Message-ID: <20260821192332.19060-4-stuart.summers@intel.com> (raw)

This series is meant to test the changes coming in with [1]. There
is a new debug specific configfs group to allow easy addition of
debug-specific configfs entries without worrying about ABI for non-debug
configurations. There are also two new entries tested here,
guc_log_level and guc_log_target.

[1]: https://patchwork.freedesktop.org/series/165879/

Stuart Summers (2):
  tests/intel/xe_configfs: Use the new debug configfs group
  tests/intel/xe_configfs: Add coverage for GuC log configfs entries

 tests/intel/xe_configfs.c | 312 ++++++++++++++++++++++++++++++++------
 1 file changed, 269 insertions(+), 43 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-08-21 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 19:23 Stuart Summers [this message]
2026-08-21 19:23 ` [PATCH i-g-t 1/2] tests/intel/xe_configfs: Use the new debug configfs group Stuart Summers
2026-08-21 19:23 ` [PATCH i-g-t 2/2] tests/intel/xe_configfs: Add coverage for GuC log configfs entries Stuart Summers
2026-08-21 21:11 ` ✓ Xe.CI.BAT: success for Test new debug based configfs changes Patchwork
2026-08-21 21:26 ` ✓ i915.CI.BAT: " Patchwork
2026-08-21 23:19 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-08-22  0:16 ` ✗ 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=20260821192332.19060-4-stuart.summers@intel.com \
    --to=stuart.summers@intel.com \
    --cc=Michal.Wajdeczko@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=shuicheng.lin@intel.com \
    --cc=umesh.nerlige.ramappa@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.