All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Farah Kassabri <farah.kassabri@intel.com>,
	 Rodrigo Vivi <rodrigo.vivi@intel.com>,
	 Gustavo Sousa <gustavo.sousa@intel.com>,
	 Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH 0/2] Add type-specific GT loop iterator
Date: Thu, 05 Mar 2026 14:59:26 -0800	[thread overview]
Message-ID: <20260305-gt-type-loops-v1-0-aa42e9fc3f06@intel.com> (raw)

Although we don't have too many GT loops in the driver today that are
restricted to a specific GT type, we expect more to show up in some
upcoming work.  Add a new iterator macro to make this slightly simpler
and convert the existing type-specific loops over to use it.

Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
---
Matt Roper (2):
      drm/xe: Add for_each_gt_with_type() iterator
      drm/xe: Utilize for_each_gt_with_type() for type-specific GT loops

 drivers/gpu/drm/xe/xe_device.c             | 5 +----
 drivers/gpu/drm/xe/xe_device.h             | 4 ++++
 drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 5 +----
 3 files changed, 6 insertions(+), 8 deletions(-)
---
base-commit: ce63d46cc8fc3bb754efb93026b55acaa616cfa2
change-id: 20260305-gt-type-loops-e8e4bc4dd19e

Best regards,
-- 
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation


             reply	other threads:[~2026-03-05 23:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 22:59 Matt Roper [this message]
2026-03-05 22:59 ` [PATCH 1/2] drm/xe: Add for_each_gt_with_type() iterator Matt Roper
2026-03-06  0:49   ` Rodrigo Vivi
2026-03-05 22:59 ` [PATCH 2/2] drm/xe: Utilize for_each_gt_with_type() for type-specific GT loops Matt Roper
2026-03-06  0:49   ` Rodrigo Vivi
2026-03-06 17:11 ` ✗ CI.checkpatch: warning for Add type-specific GT loop iterator Patchwork
2026-03-06 17:12 ` ✓ CI.KUnit: success " Patchwork
2026-03-06 18:11 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-07 19:57 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-09 21:41   ` Matt Roper

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=20260305-gt-type-loops-v1-0-aa42e9fc3f06@intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=farah.kassabri@intel.com \
    --cc=gustavo.sousa@intel.com \
    --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.