From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
intel-gfx@lists.freedesktop.org,
I915-ci-infra@lists.freedesktop.org
Cc: Gustavo Sousa <gustavo.sousa@intel.com>
Subject: Re: ✓ Fi.CI.IGT: success for drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD (rev4)
Date: Mon, 11 Nov 2024 11:20:44 +0200 [thread overview]
Message-ID: <87r07icej7.fsf@intel.com> (raw)
In-Reply-To: <20241108180821.GU4891@mdroper-desk1.amr.corp.intel.com>
On Fri, 08 Nov 2024, Matt Roper <matthew.d.roper@intel.com> wrote:
> Although I just realized I confused the i915 results with the Xe results
> and the full Xe run is still going...woops. Xe BAT was fine, but if it
> turns out there's a problem with the full Xe shard run, we can deal with
> that once we see the results.
I think the CI messaging should have more clarity on what's being run.
Fi.CI.BAT vs. CI.BAT and Fi.CI.IGT vs. CI.FULL.
You just have to know "Fi" means i915 and lack of it means xe.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-11-11 9:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 12:57 [PATCH v4 00/15] drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 01/15] drm/i915/dmc_wl: Use i915_mmio_reg_offset() instead of reg.reg Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 02/15] drm/xe: Mimic i915 behavior for non-sleeping MMIO wait Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 03/15] drm/i915/dmc_wl: Use non-sleeping variant of " Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 04/15] drm/i915/dmc_wl: Check for non-zero refcount in release work Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 05/15] drm/i915/dmc_wl: Get wakelock when disabling dynamic DC states Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 06/15] drm/i915/dmc_wl: Use sentinel item for range tables Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 07/15] drm/i915/dmc_wl: Extract intel_dmc_wl_reg_in_range() Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 08/15] drm/i915/dmc_wl: Rename lnl_wl_range to powered_off_ranges Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 09/15] drm/i915/dmc_wl: Track registers touched by the DMC Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 10/15] drm/i915/dmc_wl: Allow simpler syntax for single reg in range tables Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 11/15] drm/i915/dmc_wl: Deal with existing references when disabling Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 12/15] drm/i915/dmc_wl: Couple enable/disable with dynamic DC states Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 13/15] drm/i915/dmc_wl: Add and use HAS_DMC_WAKELOCK() Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 14/15] drm/i915/dmc_wl: Sanitize enable_dmc_wl according to hardware support Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 15/15] drm/i915/xe3lpd: Use DMC wakelock by default Gustavo Sousa
2024-11-08 13:51 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD (rev4) Patchwork
2024-11-08 13:51 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-08 14:05 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-08 14:16 ` [PATCH v4 00/15] drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD Luca Coelho
2024-11-08 14:19 ` Gustavo Sousa
2024-11-08 15:25 ` ✓ Fi.CI.IGT: success for drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD (rev4) Patchwork
2024-11-08 18:08 ` Matt Roper
2024-11-11 9:20 ` Jani Nikula [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=87r07icej7.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox